From: Rick Jones <rick.jones2@hp.com>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
johnathan@jonmasters.org, netdev@vger.kernel.org,
dwmw2@infradead.org
Subject: Re: network interface *name* alias support?
Date: Fri, 23 May 2008 10:44:10 -0700 [thread overview]
Message-ID: <4837026A.6000702@hp.com> (raw)
In-Reply-To: <4836FB73.2010709@intel.com>
> FWIW you can just use ethtool to determine the slot address quickly
> in userspace. There's no real need to do this in the kernel.
>
> # ethtool -i eth0
> driver: e1000e
> version: 0.2.0
> firmware-version: 1.3-0
> bus-info: 0000:00:19.0
And if it happens to be in a hotplug slot today with a suitable hotplug
module (term?) loaded like acpiphp you can then map that to a more human
friendly slot number/name. In the future, once Alex Chiang's pci slots
patches make it to mainline it will be possible even with non-hotplug slots.
netperf omni tests and a couple other tools try to find such mappings today.
rick jones
next prev parent reply other threads:[~2008-05-23 17:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 16:31 network interface *name* alias support? Jan Engelhardt
2008-05-23 17:14 ` Kok, Auke
2008-05-23 17:44 ` Rick Jones [this message]
2008-05-23 19:06 ` Jon Masters
2008-05-23 19:11 ` Jon Masters
2008-05-23 20:46 ` Jan Engelhardt
2008-05-23 20:55 ` Jon Masters
2008-05-23 22:54 ` Thomas Graf
2008-05-24 4:25 ` Jon Masters
2008-05-24 4:53 ` Jan Engelhardt
2008-05-24 5:16 ` Matt Domsch
2008-05-24 9:15 ` James Chapman
2008-05-24 9:33 ` David Woodhouse
2008-05-24 10:37 ` James Chapman
2008-05-24 20:31 ` Patrick McHardy
2008-05-24 20:54 ` Jan Engelhardt
2008-05-25 3:07 ` Patrick McHardy
2008-05-25 12:17 ` David Miller
2008-05-27 19:03 ` Matt Domsch
2008-05-27 21:49 ` Jan Engelhardt
2008-05-27 22:11 ` Thomas Graf
2008-05-24 18:12 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 22:47 Jon Masters
2008-05-23 13:07 ` David Woodhouse
2008-05-23 14:50 ` Jon Masters
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=4837026A.6000702@hp.com \
--to=rick.jones2@hp.com \
--cc=auke-jan.h.kok@intel.com \
--cc=dwmw2@infradead.org \
--cc=jengelh@medozas.de \
--cc=johnathan@jonmasters.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.