| To: | Steve Modica <modica@xxxxxxx> |
|---|---|
| Subject: | Re: Linking interfaces to slots |
| From: | David Brownell <david-b@xxxxxxxxxxx> |
| Date: | Fri, 03 Oct 2003 06:37:13 -0700 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <3F7D675D.4000905@xxxxxxx> |
| References: | <3F7D675D.4000905@xxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 |
Steve Modica wrote: If one wanted to figure out which ethX was in which PCI slot on which bus, what would be the most acceptable mechanism? The drivers have access to all this info, but then each driver would need some ioctl added. Is there some more generic place in the kernel that could be modified such that /proc/net/dev could hold this information? On 2.6 there's /sys/class/net/ethX/device, and ethtool_drvinfo.bus_info support should exist too... - Dave |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: e1000 -> 82540EM on linux 2.6.0-test[45] very slow in one direction, Ookhoi |
|---|---|
| Next by Date: | Re: Linking interfaces to slots, Linda Xie |
| Previous by Thread: | Linking interfaces to slots, Steve Modica |
| Next by Thread: | Re: Linking interfaces to slots, Linda Xie |
| Indexes: | [Date] [Thread] [Top] [All Lists] |