From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH 1/4] [Linux/SCSI]: Change RECEIVE_CREDENTIAL to VLC_SA_RECEIVE_CREDENTIAL
Date: Thu, 29 Jan 2009 15:31:35 -0800 [thread overview]
Message-ID: <1233271895.6442.220.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <4981972A.2090801@panasas.com>
On Thu, 2009-01-29 at 13:46 +0200, Boaz Harrosh wrote:
> Nicholas A. Bellinger wrote:
> > Hi James,
> >
> > Let me know if you need a fresh respin of this patch.. According to
> > spc4r17 section D.3.5, VLC_SA_RECEIVE_CREDENTIAL is the only
> > VARIABLE_LENGTH_CMD defined Service ACtion..
> >
> > --nab
>
> Not accurate. See file include/scsi/osd_protocol.h in the scsi-misc
> git-tree master branch. The complete OSD command set is VARIABLE_LENGTH_CMD
> based. There must be others as well
>
Ok, what I meant was:
>From searching spc4r17, VLC_SA_RECEIVE_CREDENTIAL (0x1800) is the only
SPC-4 defined VARIABLE_LENGTH_CMD defined Service Action in Table D.8.
>From SPC-4, the range 0x1800 -> 0x1FFF is reserved for SPC-4 defined
VARIABLE_LENGTH_CMD SAs.
I see that OSD SAs for VARIABLE_LENGTH_CMD opcode are defined in range
0x8800 -> 0x8FFF, so does not it make sense to add the single VLC_SA_*
prefixed define above for range 0x1800 -> 0x1FFF in
include/scsi/scsi.h..?
Many thanks for your most valuable of time,
--nab
> Boaz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-01-29 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 22:02 Nicholas A. Bellinger
2009-01-27 22:10 ` Nicholas A. Bellinger
2009-01-29 11:46 ` Boaz Harrosh
2009-01-29 23:31 ` Nicholas A. Bellinger [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=1233271895.6442.220.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®