From: Pavel Emelianov <xemul@openvz.org>
To: Ben Greear <greearb@candelatech.com>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Patrick McHardy <kaber@trash.net>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Kirill Korotaev <dev@openvz.org>,
Linux Containers <containers@lists.osdl.org>
Subject: Re: [PATCH] Virtual ethernet tunnel (v.2)
Date: Fri, 08 Jun 2007 20:00:10 +0400 [thread overview]
Message-ID: <46697D0A.40006@openvz.org> (raw)
In-Reply-To: <46682976.8050904@candelatech.com>
Ben Greear wrote:
[snip]
>>> I would also like some way to identify veth from other device types,
>>> preferably
>>> something like a value in sysfs. However, that should not hold up
>>>
>>
>> We can do this with ethtool. It can get and print the driver name of
>> the device.
>>
> I think I'd like something in sysfs that we could query for any
> interface. Possible return
> strings could be:
> VLAN
> VETH
> ETH
> PPP
> BRIDGE
> AP /* wifi access point interface */
> STA /* wifi station */
> ....
>
> I will cook up a patch for consideration after veth goes in.
>
Ben, could you please tell what sysfs features do you
plan to implement?
Thanks,
Pavel
next prev parent reply other threads:[~2007-06-08 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 11:13 [PATCH] Virtual ethernet tunnel (v.2) Pavel Emelianov
2007-06-07 11:16 ` [PATCH] Module for ip utility to support veth device (v.2) Pavel Emelianov
2007-06-07 15:59 ` Stephen Hemminger
2007-06-07 15:23 ` [PATCH] Virtual ethernet tunnel (v.2) Ben Greear
2007-06-07 15:39 ` Pavel Emelianov
2007-06-07 15:51 ` Ben Greear
2007-06-07 16:04 ` Pavel Emelianov
2007-06-07 16:35 ` Ben Greear
2007-06-08 16:00 ` Pavel Emelianov [this message]
2007-06-08 17:00 ` Ben Greear
2007-06-08 19:49 ` Carl-Daniel Hailfinger
2007-06-08 23:46 ` Ben Greear
2007-06-11 11:42 ` Patrick McHardy
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=46697D0A.40006@openvz.org \
--to=xemul@openvz.org \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=greearb@candelatech.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).