From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Predict/force PCI slot id given by the kernel to NICs
Date: Tue, 20 May 2014 17:21:26 -0400 [thread overview]
Message-ID: <30861.1400620886@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 20 May 2014 15:55:09 -0500." <CAFGHVq0F6=PzXNk1zaZL7hvTDr9hZmZw=YqMfccLy+vVggzvCg@mail.gmail.com>
On Tue, 20 May 2014 15:55:09 -0500, Jaime Arrocha said:
> I am working on a Proliant server model which have 6 physical pci slots.
> They are going to be used for NICs with either 2 or 4 interfaces and
> installed in an arbitrarily order in the slots. By this I mean that the a
> certain box will only have a card/s on only certain slots.
>
> I need to write a program to its able to predict/read what bus id (slot id)
> the kernel gives to each interface for every card. The program should be
> able to relate the bus id to the slot where it is physically installed at.
Have whatever installer program (anaconda for RH-based, etc) call an exit
script that does an 'lspci | grep your_nic_card_here'? and scribble in
the /etc/udev/rules.d file?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140520/062cd063/attachment.bin
prev parent reply other threads:[~2014-05-20 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 20:55 Predict/force PCI slot id given by the kernel to NICs Jaime Arrocha
2014-05-20 21:18 ` Greg KH
2014-05-20 21:21 ` Valdis.Kletnieks at vt.edu [this message]
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=30861.1400620886@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).