From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Dreier Subject: Re: [RFC] ib_srpt: initial .40-rc1 drivers/infiniband/ulp/srpt merge Date: Wed, 18 May 2011 12:17:21 -0700 Message-ID: References: <1305682604-21383-1-git-send-email-nab@linux-iscsi.org> <20110518170556.GB2595@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org To: Bart Van Assche Cc: Jason Gunthorpe , "Nicholas A. Bellinger" , linux-kernel , linux-scsi , linux-rmda , Vu Pham , David Dillow , James Bottomley List-Id: linux-rdma@vger.kernel.org On Wed, May 18, 2011 at 11:02 AM, Bart Van Assche 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.