[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <461A70A5.8060607@trash.net>
Date: Mon, 09 Apr 2007 18:58:13 +0200
From: Patrick McHardy <kaber@...sh.net>
To: Johannes Berg <johannes@...solutions.net>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Jeff Garzik <jgarzik@...ox.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
Ben Greear <greearb@...delatech.com>,
Daniel Lezcano <dlezcano@...ibm.com>,
Dmitry Mishin <dim@...nvz.org>,
Linux Containers <containers@...ts.osdl.org>
Subject: Re: [PATCH] net: Add etun driver
Johannes Berg wrote:
> On Fri, 2007-04-06 at 20:51 -0600, Eric W. Biederman wrote:
>
>
>>The only sysfs attributes that were always available that I could find
>>were module parameters. A little odd because we can specify them on
>>the kernel command line, or when loading the module in addition to
>>being available at run time.
>>
>>It gives me a general interface that is usable so long as the module
>>is loaded, and does not depend on the availability of any specific
>>network device. I will happily use any other interface that gives
>>me the same level of functionality for the roughly the same level
>>of effort.
>
>
> Just for consideration, in wireless we currently create virtual network
> devices by having a "add_iface" and "remove_iface" sysfs files below the
> ieee80211 class.
It would be nice if someone would finally come up with a generic
interface based on netlink (RTM_NEWLINK) instead of adding yet
another couple of homegrown interfaces.
-
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