[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 06 Jun 2007 22:38:11 +0200
From: Daniel Lezcano <dlezcano@...ibm.com>
To: David Miller <davem@...emloft.net>
CC: xemul@...nvz.org, containers@...ts.osdl.org,
netdev@...r.kernel.org, kaber@...sh.net, dev@...nvz.org
Subject: Re: [Devel] Re: [PATCH] Virtual ethernet tunnel
David Miller wrote:
> From: Pavel Emelianov <xemul@...nvz.org>
> Date: Wed, 06 Jun 2007 19:11:38 +0400
>
>
>> 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.
>>
>
> I would suggest choosing a different name.
>
> 'veth' is also the name of the virtualized ethernet device
> found on IBM machines, driven by driver/net/ibmveth.[ch]
>
Eric Biederman proposed the name "etun" which stands for "Ethernet TUNnel".
The goal of the pair device is to pass network packets between namespaces.
That reminds me the well known "pipe" which pass data between processes.
All network devices have a name describing what they do : "eth" for
ethernet,
"dummy" for a device doing nothing, loopback, ...
Perhaps, a name like "epipe" or "npipe", which reflects what does the
device, is more appropriate ?
-- Daniel
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists