From: Matt Domsch <Matt_Domsch@Dell.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: linux-hotplug@vger.kernel.org, netdev@vger.kernel.org, "K,
Narendra" <Narendra_K@Dell.com>,
"Hargrave, Jordan" <Jordan_Hargrave@Dell.com>,
"Rose, Charles" <Charles_Rose@Dell.com>,
Colin Watson <cjwatson@ubuntu.com>
Subject: Re: biosdevname v0.3.2
Date: Tue, 07 Dec 2010 18:19:10 +0000 [thread overview]
Message-ID: <20101207181910.GA2643@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <1291745782.21627.6.camel@bwh-desktop>
On Tue, Dec 07, 2010 at 06:16:22PM +0000, Ben Hutchings wrote:
> It appears that 'unknown slot' is treated as a specific slot and all
> devices with an unknown slot are given unique indices. Perhaps this
> doesn't matter in the end, since no name is generated when the slot is
> unknown.
Yes on all counts.
> However, the 2 NIC ports do have their own indices (specified with the
> dev_id attribute) and it should be possible to distinguish slots by
> PCI/PCIe topology even though the name given won't correspond to any
> markings on the motherboard.
Tell me more about the dev_id attribute. I'm happy to use it, but I
don't understand the rules around populating it.
Thanks,
Matt
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
WARNING: multiple messages have this Message-ID (diff)
From: Matt Domsch <Matt_Domsch@Dell.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: linux-hotplug@vger.kernel.org, netdev@vger.kernel.org, "K,
Narendra" <Narendra_K@Dell.com>,
"Hargrave, Jordan" <Jordan_Hargrave@Dell.com>,
"Rose, Charles" <Charles_Rose@Dell.com>,
Colin Watson <cjwatson@ubuntu.com>
Subject: Re: biosdevname v0.3.2
Date: Tue, 7 Dec 2010 12:19:10 -0600 [thread overview]
Message-ID: <20101207181910.GA2643@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <1291745782.21627.6.camel@bwh-desktop>
On Tue, Dec 07, 2010 at 06:16:22PM +0000, Ben Hutchings wrote:
> It appears that 'unknown slot' is treated as a specific slot and all
> devices with an unknown slot are given unique indices. Perhaps this
> doesn't matter in the end, since no name is generated when the slot is
> unknown.
Yes on all counts.
> However, the 2 NIC ports do have their own indices (specified with the
> dev_id attribute) and it should be possible to distinguish slots by
> PCI/PCIe topology even though the name given won't correspond to any
> markings on the motherboard.
Tell me more about the dev_id attribute. I'm happy to use it, but I
don't understand the rules around populating it.
Thanks,
Matt
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
next prev parent reply other threads:[~2010-12-07 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 14:06 biosdevname v0.3.2 Matt Domsch
2010-12-06 14:06 ` Matt Domsch
2010-12-07 18:16 ` Ben Hutchings
2010-12-07 18:19 ` Matt Domsch [this message]
2010-12-07 18:19 ` Matt Domsch
2010-12-07 18:41 ` Ben Hutchings
2010-12-08 5:19 ` Matt Domsch
2010-12-08 5:19 ` Matt Domsch
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=20101207181910.GA2643@auslistsprd01.us.dell.com \
--to=matt_domsch@dell.com \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=bhutchings@solarflare.com \
--cc=cjwatson@ubuntu.com \
--cc=linux-hotplug@vger.kernel.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.