All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	linux-scsi@vger.kernel.org, jens.axboe@oracle.com,
	James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [PATCH 0/8] target mode support
Date: Thu, 16 Nov 2006 12:18:48 -0500	[thread overview]
Message-ID: <455C9D78.7020400@emulex.com> (raw)
In-Reply-To: <455C9299.5010202@cs.wisc.edu>

Ok.  My assumption is that it is preferred to be a single mode, but that
dual mode should be supported.  Please note that dual mode may impact some
of the feature set in the emulated target - and it'll be a trick to identify
that.

Hmm... what this leads me to is - there is a difference between the
pure SCSI behavior (performing a SCSI Read command), and the transport-level
SCSI behavior (Mode Pages; FCP: Conf, Recovery; iSCSI CmdSN/StatSN progression,
SNACK, RSP retransmission, etc). Although, these will be very tightly
integrated.  How does this code account for this ?  Are there transport-level
libraries in-between the LLDD and the SCSI Target ? Is it reflected in the
LLDD to SCSI Target messaging ?

-- james


Mike Christie wrote:
> James Smart wrote:
>> One question....
>>
>> Does this assume that an hba is both initiator and target ?  target only ?
>> Do we have any issues if a scsi_host is a target only ?
>>
> 
> I do not think that is fully worked out yet. The only target that is
> done is the vscsi one which is a little different from something like
> lpfc or qla*. I think some developers like Qlogic would prefer the
> driver and card is only in one mode or the other to simplify things.
> However, I think Tomo and users would like to be able to use a
> card/driver in both modes at the same time.
> 

  reply	other threads:[~2006-11-16 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 10:23 [PATCH 0/8] target mode support FUJITA Tomonori
2006-11-16 14:33 ` James Smart
2006-11-16 16:32   ` Mike Christie
2006-11-16 17:18     ` James Smart [this message]
2006-11-16 18:56       ` Mike Christie
2006-11-18  6:56   ` FUJITA Tomonori
2006-11-18 15:11     ` James Smart

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=455C9D78.7020400@emulex.com \
    --to=james.smart@emulex.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jens.axboe@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.