[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64127ea9-7021-6af9-ff00-0f1e57d8c39b@redhat.com>
Date: Thu, 14 Sep 2017 12:12:50 +0800
From: Jason Wang <jasowang@...hat.com>
To: sainath.grandhi@...el.com, netdev@...r.kernel.org
Cc: davem@...emloft.net
Subject: Re: [PATCH RFC v1 0/3] Support for tap user-space access with veth
interfaces
On 2017年09月07日 08:34, sainath.grandhi@...el.com wrote:
> 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
>
Interesting, plan to add vhost support for this? And we can enable
zerocopy without any worries I think.
Thanks
Powered by blists - more mailing lists