linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Liran Schour <LIRANS@il.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: Support for CDB length > 16
Date: Tue, 18 Nov 2003 23:02:37 +1000	[thread overview]
Message-ID: <3FBA186D.2060907@torque.net> (raw)
In-Reply-To: <OF1494DF8F.2FB4A44D-ONC2256DE2.004036A3-C2256DE2.0040B333@il.ibm.com>

Liran Schour wrote:
> 
> 
> 
> Christoph Hellwig wrote:
> 
> 
>>You'd have to enlarge MAX_COMMAND_SIZE, that'S the whole point of it :)
>>What exactly are you trying to do and for what kernel release?  We've
>>been through increasing it from 12 to 16 at some point in 2.4.
> 
> 
> I am trying to find a way to do that without the need to recompile the
> kernel.
> I am trying to support an OSD device see t10 OSD draft, I think that 2.6 is
> my target kernel release.

Liran,
Yep, I knew that I'd seen really big SCSI commands somewhere.
OSD, now there is a storage paradigm that doesn't fit
the block subsystem:-)

Perhaps we should starting thinking about kmalloc()ing
scsi_cmnd::cmnd (rather than having it as a fixed array).
The mid-level owns that structure so it can take care
of allocation and de-allocation. We would have to
find code that does sizeof(scsi_cmnd::cmnd) and fix it.

Doug Gilbert




  reply	other threads:[~2003-11-18 13:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18  8:49 Support for CDB length > 16 Liran Schour
2003-11-18  9:33 ` Douglas Gilbert
2003-11-18 11:15   ` Liran Schour
2003-11-18 11:44     ` Christoph Hellwig
2003-11-18 11:21   ` Andre Hedrick
2003-11-18 11:31 ` Christoph Hellwig
2003-11-18 11:46   ` Liran Schour
2003-11-18 13:02     ` Douglas Gilbert [this message]
2003-11-18 17:46       ` Christoph Hellwig

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=3FBA186D.2060907@torque.net \
    --to=dougg@torque.net \
    --cc=LIRANS@il.ibm.com \
    --cc=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).