From: Roland Dreier <roland@purestorage.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
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: Wed, 18 May 2011 12:17:21 -0700 [thread overview]
Message-ID: <BANLkTi==bZ0h3o5FNrg8PSJFp6F-zh5hTA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimQXU0u5gtRzXsnsB=sCF-bvpY+Ag@mail.gmail.com>
On Wed, May 18, 2011 at 11:02 AM, Bart Van Assche <bvanassche@acm.org> wrote:
> Thanks for the feedback. I'm still wondering though about the
> usefulness of disabling / enabling SRPT per HCA port. For the use
> cases I know about SRP communication over all target ports will be
> enabled as soon as target configuration has finished and more
> fine-grained access configuration will occur by allowing/disallowing
> certain initiators to log in.
I definitely think that allowing the flexibility to configure ports individually
is required. It's easy to imagine a case with a separate front-end and
back-end networks on the two HCA ports (this would be a pretty normal
ethernet config), where only one port should be a target port.
It may not be how people do things now but it should at least be possible.
- R.
next prev parent reply other threads:[~2011-05-18 19:17 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 [this message]
2011-05-19 4:18 ` Nicholas A. Bellinger
2011-05-19 10:40 ` Bart Van Assche
2011-05-19 16:57 ` Jason Gunthorpe
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='BANLkTi==bZ0h3o5FNrg8PSJFp6F-zh5hTA@mail.gmail.com' \
--to=roland@purestorage.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--cc=dillowda@ornl.gov \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--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).