public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: Seokmann Ju <seokmann.ju@qlogic.com>
Cc: Robert W Love <robert.w.love@intel.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Boaz Harrosh <bharrosh@panasas.com>,
	Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [RFC] pass through support in fc transport: via bsg (block SG)
Date: Thu, 11 Sep 2008 09:44:23 -0400	[thread overview]
Message-ID: <48C920B7.1020704@emulex.com> (raw)
In-Reply-To: <4627F04F-2980-4C9B-AED7-891452BA84E2@qlogic.com>

Seokmann,

I apologize for the late review. I'm going over it now. (PS: ping me 
next time if you want to makre sure I've looked at it). I should have 
comments within the day.

Seokmann Ju wrote:
> I actually had missed the point at that time and now I'm getting it as
> I read one more time.
> So, in this case, how to identify whether the request is ELS or CT if
> the application issues the request without the frame header?

Whether it's ELS or CT should be part of the metadata of the request (a 
flag, a request type opcode, or similar).  There should be no reason for 
a frame header.

-- james s


      reply	other threads:[~2008-09-11 13:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 19:04 [RFC] pass through support in fc transport: via bsg (block SG) Seokmann Ju
2008-08-19 17:42 ` Seokmann Ju
2008-08-22 21:36   ` Seokmann Ju
2008-08-22 21:53     ` James Smart
2008-08-22 22:09       ` Andrew Vasquez
2008-08-22 22:35         ` Chris Leech
2008-08-22 22:48           ` Andrew Vasquez
2008-08-23 14:43         ` James Smart
2008-09-11 13:25       ` Seokmann Ju
2008-09-11 13:44         ` James Smart [this message]

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=48C920B7.1020704@emulex.com \
    --to=james.smart@emulex.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=robert.w.love@intel.com \
    --cc=seokmann.ju@qlogic.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