linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Liran Liss <liranl-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Tzahi Oved <tzahio-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: RDMA miniconf: Persistent device naming
Date: Mon, 31 Jul 2017 14:36:33 +0300	[thread overview]
Message-ID: <20170731113633.GU13672@mtr-leonro.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 677 bytes --]

Hi All,

I would like to propose the discussion about ability to add
persistent device naming to RDMA subsystem.

Right now, the devices receive their names by simple addition of new free
index to the name (mlx5_0, mlx5_1 ...). Such naming scheme depends on the
PCI probing and in case of device reset can rename device.

Such situation doesn't help to provide constant udev rules, reliable
ibverbs hotplug and advanced "set command" of RDMAtool which at some
point of time will require reinit of ib_device.

In this discussion, I want to present netdev implementation of such
feature, talk about implications on libibverbs and suggest possible
device name convention.

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2017-07-31 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 11:36 Leon Romanovsky [this message]
     [not found] ` <20170731113633.GU13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-31 13:48   ` RDMA miniconf: Persistent device naming Dennis Dalessandro
2017-07-31 15:00   ` Bart Van Assche
     [not found]     ` <1501513246.2466.1.camel-Sjgp3cTcYWE@public.gmane.org>
2017-07-31 16:00       ` Leon Romanovsky
2017-07-31 16:47       ` Jason Gunthorpe
     [not found]         ` <20170731164705.GB28204-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-31 16:54           ` Leon Romanovsky
     [not found]             ` <20170731165453.GD13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-31 17:00               ` Jason Gunthorpe
     [not found]                 ` <20170731170018.GA19061-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-31 17:08                   ` Leon Romanovsky
     [not found]                     ` <20170731170804.GE13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-31 17:24                       ` Jason Gunthorpe
     [not found]                         ` <20170731172436.GA19375-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-07-31 17:38                           ` Leon Romanovsky
     [not found]                             ` <20170731173813.GH13672-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-07-31 17:43                               ` Jason Gunthorpe
     [not found]                                 ` <20170731174312.GA20133-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-08-01  6:24                                   ` Leon Romanovsky

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=20170731113633.GU13672@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=liranl-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=tzahio-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 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).