mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Anthony Samsung <anthony.samsung@gmail.com>
Subject: Re: network interface to driver and pci slot mapping
Date: Thu, 11 Nov 2004 13:49:57 -0800	[thread overview]
Message-ID: <20041111214956.GA10283@bougret.hpl.hp.com> (raw)

Anthony Samsung wrote :
> 
> Given an interface name (like eth0), how do I determine:
> The name of the driver (module) for this interface.
> The PCI address for this interface, if relevant.
> 
> ?

	ethtool -i. Unfortunately, not yet implemented in all driver,
but Jeff is on the case.
	There might also be a sysfs way to do it, but it probably
involve lot's a grep or similar magic.

> I need something that works non-destructively on a live system, that
> isn't broken by nameif, and has a strong chance of producing a correct
> result. In particular, parsing syslog is out. There's no consistency
> in the format of messages and there's no guarantee the logs from
> bootup will still be around. And the interface may have been renamed
> since then.

	ifrename allow you to rename interfaces based on both driver
name and PCI address, so another option is to make sure interface
names are consistent and meaningful.

	Have fun...

	Jean

             reply	other threads:[~2004-11-11 21:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 21:49 Jean Tourrilhes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-11 21:28 Anthony Samsung
2004-11-11 21:48 ` linux-os
2004-11-11 22:34   ` Måns Rullgård
2004-11-11 22:51     ` Jeff Garzik
2004-11-12  0:56 ` Greg KH
2004-11-12  3:43   ` Daniel Stekloff

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=20041111214956.GA10283@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=anthony.samsung@gmail.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®