| 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@xxxxxxxxxxxxx> |
| Organization: | Open Source Development Lab |
| References: | <424C6089.1080507@xxxxxxxxxxxxxxx> <20050331130512.7e4b8bc0@xxxxxxxxxxxxxxxxx> <424C6F82.7030609@xxxxxxxxxxxxxxx> <20050331135229.432afff3.davem@xxxxxxxxxxxxx> |
| 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> |
|---|---|---|
| ||
| Previous by Date: | Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics, Dmitry Yusupov |
|---|---|
| Next by Date: | Re: RFC: Redirect-Device, David S. Miller |
| Previous by Thread: | Re: RFC: Redirect-Device, David S. Miller |
| Next by Thread: | Re: RFC: Redirect-Device, Ben Greear |
| Indexes: | [Date] [Thread] [Top] [All Lists] |