netdev
[Top] [All Lists]

Re: RFC: Redirect-Device

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: RFC: Redirect-Device
From: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Thu, 31 Mar 2005 14:05:25 -0800
Cc: Ben Greear <greearb@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <20050331135229.432afff3.davem@davemloft.net>
Organization: Open Source Development Lab
References: <424C6089.1080507@candelatech.com> <20050331130512.7e4b8bc0@dxpl.pdx.osdl.net> <424C6F82.7030609@candelatech.com> <20050331135229.432afff3.davem@davemloft.net>
Sender: netdev-bounce@xxxxxxxxxxx
On Thu, 31 Mar 2005 13:52:29 -0800
"David S. Miller" <davem@xxxxxxxxxxxxx> wrote:

> On Thu, 31 Mar 2005 13:45:38 -0800
> Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote:
> 
> > >   Adding new ioctl's are very frowned on
> > 
> > Bummer.  I want these as well, makes programatic reading of the information
> > much easier than trying to parse some proc file.  I will look into what it
> > takes to make them compat with 64-bit as DaveM suggested.
> 
> You could extend and use ethtool.  That is what it's there for.

Other possiblity is adding additional attributes onto the device with sysfs.
That is what net/bridge/br_sysfs_if.c does. I'm not claiming it is a pretty
kernel programming model, but the user side API is simpler.


<Prev in Thread] Current Thread [Next in Thread>