From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Roland Dreier <roland@purestorage.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-rmda <linux-rdma@vger.kernel.org>,
Vu Pham <vu@mellanox.com>, David Dillow <dillowda@ornl.gov>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [RFC] ib_srpt: initial .40-rc1 drivers/infiniband/ulp/srpt merge
Date: Thu, 19 May 2011 10:57:28 -0600 [thread overview]
Message-ID: <20110519165728.GB12525@obsidianresearch.com> (raw)
In-Reply-To: <BANLkTi=Xb-ypQNa3=MmwiLeE4Q9FWHnZXg@mail.gmail.com>
On Thu, May 19, 2011 at 12:40:02PM +0200, Bart Van Assche wrote:
> I'm still wondering whether it was a good idea to switch from ib<n>
> style names to port GIDs. Not only will that make it hard for users to
> match the ib<n> names already assigned to InfiniBand HCAs with target
> port names but this also deviates from the naming scheme used for any
> other Linux device. Ethernet devices e.g. appear as eth<n> in /dev
> instead of a MAC address like 00:1a:64:10:18:6f.
The ib# names returned by ip addr are already disjoint from the
namespace that is being used by SRP targets. The only choices are port
GUID or something like mlx4_0/1, the later is somewhat less
commonly used..
Is there some approach here for selecting the pkey as well?
Jason
next prev parent reply other threads:[~2011-05-19 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 1:36 [RFC] ib_srpt: initial .40-rc1 drivers/infiniband/ulp/srpt merge Nicholas A. Bellinger
2011-05-18 7:47 ` Christoph Hellwig
2011-05-18 16:46 ` Roland Dreier
2011-05-19 6:00 ` Nicholas A. Bellinger
2011-05-18 16:59 ` Bart Van Assche
2011-05-18 17:05 ` Jason Gunthorpe
2011-05-18 18:02 ` Bart Van Assche
2011-05-18 19:17 ` Roland Dreier
2011-05-19 4:18 ` Nicholas A. Bellinger
2011-05-19 10:40 ` Bart Van Assche
2011-05-19 16:57 ` Jason Gunthorpe [this message]
2011-05-19 20:03 ` Nicholas A. Bellinger
2011-05-19 17:29 ` Bart Van Assche
2011-05-19 17:44 ` Jason Gunthorpe
2011-05-19 18:34 ` Bart Van Assche
2011-05-19 18:41 ` Jason Gunthorpe
2011-05-22 19:14 ` Bart Van Assche
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=20110519165728.GB12525@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=dillowda@ornl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=roland@purestorage.com \
--cc=vu@mellanox.com \
/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).