[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <461A89DF.1030307@trash.net>
Date: Mon, 09 Apr 2007 20:45:51 +0200
From: Patrick McHardy <kaber@...sh.net>
To: Ben Greear <greearb@...delatech.com>
CC: Johannes Berg <johannes@...solutions.net>,
"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>,
Daniel Lezcano <dlezcano@...ibm.com>,
Dmitry Mishin <dim@...nvz.org>,
Linux Containers <containers@...ts.osdl.org>
Subject: Re: [PATCH] net: Add etun driver
Ben Greear wrote:
> Patrick McHardy wrote:
>
>> 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.
>
>
> My preference is for ioctls, procfs, or similar that does not
> require extra libraries. Ethtool is an ioctl based approach,
> so that could potentially be used, though I'm not sure if
> that's the right place to put it...
Extra libraries is one of the least important points in my opinion,
I also guess pretty much anyone using a software device already has
iproute installed, which could easily support all of them.
The more important things to consider are in my opinion extendability
and atomicity of changes and dumps:
- ioctls: atomicity, not easily extendable
- sysfs: no atomicity, easily extendable
- procfs: if atomicity not easily extendable, but can of course also
be used similar to sysfs
Only netlink offers both in an easy to use fashion and is already used
for the main parts of network configuration anyway.
-
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