[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2C5142675EC1274EAB6230F72F8DC95F6C101F1F@ORSMSX113.amr.corp.intel.com>
Date: Wed, 20 Sep 2017 02:38:11 +0000
From: "Grandhi, Sainath" <sainath.grandhi@...el.com>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>
Subject: RE: [PATCH RFC v1 0/3] Support for tap user-space access with veth
interfaces
Just a reminder for feedback.
> -----Original Message-----
> From: Grandhi, Sainath
> Sent: Wednesday, September 06, 2017 5:34 PM
> To: netdev@...r.kernel.org
> Cc: davem@...emloft.net; Grandhi, Sainath <sainath.grandhi@...el.com>
> Subject: [PATCH RFC v1 0/3] Support for tap user-space access with veth
> interfaces
>
> From: Sainath Grandhi <sainath.grandhi@...el.com>
>
> This patchset adds a tap device driver for veth virtual network interface.
> With this implementation, tap character interface can be added only to the peer
> veth interface. Adding tap interface to veth is for usecases that forwards
> packets between host and VMs. This eliminates the need for an additional
> software bridge. This can be extended to create both the peer interfaces as tap
> interfaces. These patches are a step in that direction.
>
> Sainath Grandhi (3):
> net: Adding API to parse IFLA_LINKINFO attribute
> net: Abstracting out common routines from veth for use by vethtap
> vethtap: veth based tap driver
>
> drivers/net/Kconfig | 1 +
> drivers/net/Makefile | 2 +
> drivers/net/{veth.c => veth_main.c} | 80 ++++++++++---
> drivers/net/vethtap.c | 216 ++++++++++++++++++++++++++++++++++++
> include/linux/if_veth.h | 13 +++
> include/net/rtnetlink.h | 3 +
> net/core/rtnetlink.c | 8 ++
> 7 files changed, 308 insertions(+), 15 deletions(-) rename drivers/net/{veth.c =>
> veth_main.c} (89%) create mode 100644 drivers/net/vethtap.c create mode
> 100644 include/linux/if_veth.h
>
> --
> 2.7.4
Powered by blists - more mailing lists