linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: lsf-pc <lsf-pc@lists.linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	target-devel <target-devel@vger.kernel.org>
Cc: Roland Dreier <roland@kernel.org>, Christoph Hellwig <hch@lst.de>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Madhu Iyengar <madhu.iyengar@qlogic.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Hannes Reinecke <mail@hannes-reinecke.de>
Subject: [LSF/MM TOPIC] [ATTEND] qla2xxx FC target mode
Date: Sat, 28 Jan 2012 16:27:49 -0800	[thread overview]
Message-ID: <1327796869.18763.211.camel@haakon2.linux-iscsi.org> (raw)

Hello,

Given the interest getting the Qlogic FC Target driver merged into
mainline during the v3.4 -> v3.5 time frame, I would like to propose a
LSF storage track discussion for some of the longer term items wrt
qla2xxx target mode that are stretching across SCSI + target subsystems.

We would like to eventually support mixed SCSI initiator / target mode
on a per HW port context basis.  Before that can happen in mainline some
of the interaction between SCSI core and target core will need to be
sorted out..

This includes:

- I -> T transition between active initiator mode LLD LUNs 
  + active TCM ports in same LLD
- T -> I transition + rescan of ports without having to restart SCSI LLD
- mixed mode running on the same physical/virtual port
- target core dependencies in SCSI core to make this work..?

More background is available in the RFC-v4 posting here:
http://www.spinics.net/lists/target-devel/msg01424.html

Thanks!

--nab

             reply	other threads:[~2012-01-29  0:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29  0:27 Nicholas A. Bellinger [this message]
2012-03-16 23:40 ` [LSF/MM TOPIC] [ATTEND] qla2xxx FC target mode Nicholas A. Bellinger
2012-03-18  9:22   ` [Lsf-pc] " James Bottomley
2012-03-19  0:22     ` Nicholas A. Bellinger
2012-03-19  8:54       ` James Bottomley
2012-03-20  0:15         ` Nicholas A. Bellinger
2012-03-20  9:03           ` James Bottomley
2012-03-21  4:12             ` Nicholas A. Bellinger

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=1327796869.18763.211.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=madhu.iyengar@qlogic.com \
    --cc=mail@hannes-reinecke.de \
    --cc=roland@kernel.org \
    --cc=target-devel@vger.kernel.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).