From: Pavel Emelyanov <xemul@openvz•org>
To: David Miller <davem@davemloft•net>
Cc: Patrick McHardy <kaber@trash•net>,
Linux Netdev List <netdev@vger•kernel.org>,
devel@openvz•org
Subject: Re: [PATCH] Virtual ethernet device (v.4)
Date: Wed, 08 Aug 2007 14:42:50 +0400 [thread overview]
Message-ID: <46B99E2A.60505@openvz.org> (raw)
In-Reply-To: <469F2DE7.9090407@openvz.org>
Hi, David.
What are your plans about this driver?
Thanks,
Pavel
> Veth stands for Virtual ETHernet. It is a simple tunnel driver
> that works at the link layer and looks like a pair of ethernet
> devices interconnected with each other.
>
> Mainly it allows to communicate between network namespaces but
> it can be used as is as well. E.g. one may join to bridged
> networking segments together.
>
> Eric recently sent a similar driver called etun with the sysfs
> interface. This implementation uses another interface - the RTM_NRELINK
> message introduced by Patric.
>
> The newlink callback is organized that way to make it easy to create the
> peer device in the separate namespace when we have them in kernel.
>
> Many thanks to Patrick for reviewing the patches and his advises
> on how to make driver cleaner.
>
> Changes from v.3:
> * Reserved place for struct ifinfomsg in IFLA_INFO_DATA part
> of the packet. This is not used yet, but may be in the
> future.
>
> Changes from v.2.1:
> * Made the generic routine for link creation to be used
> by veth driver, any other tunnel driver that needs to
> create several devices at once and rtnl_newlink() code.
>
> Changes from v.2:
> * Rebase over latest netdev tree. No actual changes;
> * Small code rework.
>
> Changes from v.1:
> * Per-cpu statistics;
> * Standard convention for nla policy names;
> * Module alias added;
> * Xmit function fixes noticed by Patric;
> * Code cleanup.
>
> The patch for an ip utility is also provided.
>
> Signed-off-by: Pavel Emelianov <xemul@openvz•org>
> Acked-by: Patrick McHardy <kaber@trash•net>
>
next prev parent reply other threads:[~2007-08-08 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 9:24 [PATCH] Virtual ethernet device (v.4) Pavel Emelyanov
2007-07-19 9:26 ` [PATCH 1/2] Introduce the generic rtnl_create_link() Pavel Emelyanov
2007-07-19 9:28 ` [PATCH 2/2] Virtual ethernet device driver Pavel Emelyanov
2007-07-19 9:30 ` [PATCH] Module for ip utility to support veth device (v.3) Pavel Emelyanov
2007-07-19 9:32 ` [PATCH 1/2] Introduce iplink_parse() routine Pavel Emelyanov
2007-07-19 9:33 ` [PATCH 2/2] Module for ip utility to support veth device Pavel Emelyanov
2007-08-08 10:42 ` Pavel Emelyanov [this message]
2007-08-09 5:18 ` [PATCH] Virtual ethernet device (v.4) 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=46B99E2A.60505@openvz.org \
--to=xemul@openvz$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=devel@openvz$(echo .)org \
--cc=kaber@trash$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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