From: Sainath Grandhi <sainath.grandhi@intel.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, mahesh@bandewar.net,
linux-kernel@vger.kernel.org, sainath.grandhi@intel.com
Subject: [PATCHv2 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces
Date: Tue, 17 Jan 2017 16:02:59 -0800 [thread overview]
Message-ID: <1484697786-50323-1-git-send-email-sainath.grandhi@intel.com> (raw)
Tap character devices can be implemented on other virtual interfaces like
ipvlan, similar to macvtap. Source code for tap functionality in macvtap
can be re-used for this purpose.
This patch series splits macvtap source into two modules, macvtap and tap.
This patch series also includes a patch for implementing tap character
device driver based on the IP-VLAN network interface, called ipvtap.
These patches are tested on x86 platform.
Sainath Grandhi (7):
TAP: Refactoring macvtap.c
TAP: Renaming tap related APIs, data structures, macros
TAP: Tap character device creation/destroy API
TAP: Abstract type of virtual interface from tap implementation
TAP: Extending tap device create/destroy APIs
TAP: tap as an independent module
IPVTAP: IP-VLAN based tap driver
drivers/net/Kconfig | 28 +
drivers/net/Makefile | 2 +
drivers/net/ipvlan/Makefile | 1 +
drivers/net/ipvlan/ipvlan.h | 7 +
drivers/net/ipvlan/ipvlan_core.c | 5 +-
drivers/net/ipvlan/ipvlan_main.c | 27 +-
drivers/net/ipvlan/ipvtap.c | 238 +++++++
drivers/net/macvlan.c | 2 +-
drivers/net/macvtap.c | 1226 ++----------------------------------
drivers/net/tap.c | 1262 ++++++++++++++++++++++++++++++++++++++
drivers/vhost/Kconfig | 2 +-
drivers/vhost/net.c | 3 +-
include/linux/if_macvlan.h | 17 +-
include/linux/if_tap.h | 75 +++
14 files changed, 1686 insertions(+), 1209 deletions(-)
create mode 100644 drivers/net/ipvlan/ipvtap.c
create mode 100644 drivers/net/tap.c
create mode 100644 include/linux/if_tap.h
--
2.7.4
next reply other threads:[~2017-01-18 0:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 0:02 Sainath Grandhi [this message]
2017-01-18 0:03 ` [PATCHv2 1/7] TAP: Refactoring macvtap.c Sainath Grandhi
2017-01-18 0:03 ` [PATCHv2 2/7] TAP: Renaming tap related APIs, data structures, macros Sainath Grandhi
2017-01-18 0:03 ` [PATCHv2 3/7] TAP: Tap character device creation/destroy API Sainath Grandhi
2017-01-18 21:26 ` David Miller
2017-01-19 23:33 ` Grandhi, Sainath
2017-01-18 0:03 ` [PATCHv2 4/7] TAP: Abstract type of virtual interface from tap implementation Sainath Grandhi
2017-01-18 21:27 ` David Miller
2017-01-18 0:03 ` [PATCHv2 5/7] TAP: Extending tap device create/destroy APIs Sainath Grandhi
2017-01-18 1:00 ` Andy Shevchenko
2017-01-18 0:03 ` [PATCHv2 6/7] TAP: tap as an independent module Sainath Grandhi
2017-01-18 0:03 ` [PATCHv2 7/7] IPVTAP: IP-VLAN based tap driver Sainath Grandhi
2017-01-18 21:28 ` David Miller
2017-01-19 23:33 ` Grandhi, Sainath
-- strict thread matches above, loose matches on Subject: below --
2017-01-17 23:57 [PATCHv2 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces Sainath Grandhi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1484697786-50323-1-git-send-email-sainath.grandhi@intel.com \
--to=sainath.grandhi@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh@bandewar.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).