From: David Brownell <david-b@pacbell.net>
To: Steve Modica <modica@sgi.com>
Cc: netdev@oss.sgi.com
Subject: Re: Linking interfaces to slots
Date: Fri, 03 Oct 2003 06:37:13 -0700 [thread overview]
Message-ID: <3F7D7B89.7090406@pacbell.net> (raw)
In-Reply-To: <3F7D675D.4000905@sgi.com>
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
next prev parent reply other threads:[~2003-10-03 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 12:11 Linking interfaces to slots Steve Modica
2003-10-03 13:37 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 13:39 Linda Xie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F7D7B89.7090406@pacbell.net \
--to=david-b@pacbell.net \
--cc=modica@sgi.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).