From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Shlomo Pongratz <shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: if/how to dictate IB device name per PCI BDF
Date: Fri, 12 Oct 2012 16:43:32 -0600 [thread overview]
Message-ID: <20121012224332.GB25541@obsidianresearch.com> (raw)
In-Reply-To: <5076A755.30605-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Thu, Oct 11, 2012 at 01:02:45PM +0200, Or Gerlitz wrote:
> Thinking about this a bit, will it be possible to provide a udev
> rulethat can dictate to the IB core what name / suffix digit to
> assign for a device with certain BDF?
FWIW, I reflected on this once (I belive it was for the netlink
discussion).. Allowing for a device to be renamed creates a serious
problem for RDMA since there isn't a stable 'if-index' like way for
software to refer to it.
The udev rules all rely on a means to rename the device once the
kernel has created it.
For this reason, all the software I've built uses the port GID to ID
the resource for bind/etc and strongly discourages use of the RDMA
device name.
The ipoib devices should already be renamable via udev rules, though
has anyone checked that udev doesn't have a problem with the long 'MAC'?
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-12 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 11:02 if/how to dictate IB device name per PCI BDF Or Gerlitz
[not found] ` <5076A755.30605-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-10-12 22:43 ` Jason Gunthorpe [this message]
[not found] ` <20121012224332.GB25541-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-10-12 23:04 ` Ira Weiny
[not found] ` <20121012160418.385ace32ddde5379381d5889-i2BcT+NCU+M@public.gmane.org>
2012-10-12 23:38 ` Jason Gunthorpe
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=20121012224332.GB25541@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=shlomop-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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.