All of lore.kernel.org
 help / color / mirror / Atom feed
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: [PATCHv3 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces
Date: Mon, 30 Jan 2017 11:11:55 -0800	[thread overview]
Message-ID: <1485803522-16564-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      |  241 ++++++++
 drivers/net/macvlan.c            |    2 +-
 drivers/net/macvtap.c            | 1229 ++-----------------------------------
 drivers/net/tap.c                | 1261 ++++++++++++++++++++++++++++++++++++++
 drivers/vhost/Kconfig            |    2 +-
 drivers/vhost/net.c              |    3 +-
 include/linux/if_macvlan.h       |   17 +-
 include/linux/if_tap.h           |   75 +++
 14 files changed, 1691 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

             reply	other threads:[~2017-01-30 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 19:11 Sainath Grandhi [this message]
2017-01-30 19:11 ` [PATCHv3 1/7] tap: Refactoring macvtap.c Sainath Grandhi
2017-01-30 19:11 ` [PATCHv3 2/7] tap: Renaming tap related APIs, data structures, macros Sainath Grandhi
2017-01-30 19:11 ` [PATCHv3 3/7] tap: Tap character device creation/destroy API Sainath Grandhi
2017-01-30 19:11 ` [PATCHv3 4/7] tap: Abstract type of virtual interface from tap implementation Sainath Grandhi
2017-01-30 19:12 ` [PATCHv3 5/7] tap: Extending tap device create/destroy APIs Sainath Grandhi
2017-01-31 17:51   ` David Miller
2017-02-02 23:22     ` Grandhi, Sainath
2017-01-30 19:12 ` [PATCHv3 6/7] tap: tap as an independent module Sainath Grandhi
2017-01-30 19:12 ` [PATCHv3 7/7] ipvtap: IP-VLAN based tap driver Sainath Grandhi
  -- strict thread matches above, loose matches on Subject: below --
2017-01-25 21:25 [PATCHv3 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces Sainath Grandhi
2017-01-26  4:06 ` David Miller

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=1485803522-16564-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.