public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: "Kristian Høgsberg" <krh@bitplanet.net>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux1394-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] ieee1394: sbp2: lower block queue alignment requirement
Date: Mon, 15 Jan 2007 13:50:28 -0600	[thread overview]
Message-ID: <45ABDB04.1050307@cs.wisc.edu> (raw)
In-Reply-To: <59ad55d30701151139w6176e785g53404d7b3a42ce6e@mail.gmail.com>

Kristian Høgsberg wrote:
> On 1/14/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> On 14 Jan, James Bottomley wrote:
>> > The block layer currently provides sector (512) byte alignment
>> > guarantees.  However, there has been talk in SCSI of reducing that to
>> > word (4) since that's what most intelligent PCI controllers can cope
>> > with.  If you have any alignment constraints, they should be expressed
>> > in the slave configure.
>>
>> OK, thanks. I will keep the explicit setting of the mask then.
>> I actually think that everything should work just fine with 4 bytes
>> alignment, but the SBP-2 spec mentiones 8 bytes alignment for the S/G
>> tables.  So maybe device firmwares will expect it that way even though
>> IEEE 1394 doesn't impose such a restriction even on transfers with a
>> payload of a multiple of 8 bytes.
> 
> Do you have a reference to this 8 byte alignment requirement?  I
> couldn't find it browsing through the standard.  Also, since the SBP-2
> driver has to  convert the scatterlist to an SBP-2 page table, it can
> just allocate the page table on a 8-byte boundary if that is required.
> The entries in the scatter table have no alignment restrictions from
> the SBP-2 side.
> 
> By the way, is there a way to ask the SCSI stack to limit the size of
> the entries in the scatterlist to 64k?  This would greatly simplify
> the conversion to SBP-2 page tables, since this is the maximum size
> these can hold.
> 

I think 64k is the limit already, but I think you can call
blk_queue_max_segment_size in your scsi_host_template->slave_configure
or slave_alloc to set the size to whatever you like.
-
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

  reply	other threads:[~2007-01-15 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 18:45 [PATCH] ieee1394: sbp2: lower block queue alignment requirement Stefan Richter
2007-01-14 19:19 ` James Bottomley
2007-01-14 20:14   ` Stefan Richter
2007-01-15 19:39     ` Kristian Høgsberg
2007-01-15 19:50       ` Mike Christie [this message]
2007-01-15 20:02       ` Stefan Richter
2007-01-15 21:24         ` James Bottomley
2007-01-25 21:35   ` Stefan Richter
2007-02-04 12:04     ` [PATCH] ieee1394: sbp2: remove unnecessary alignments of struct members Stefan Richter
2007-02-04 12:05       ` [PATCH] ieee1394: sbp2: enforce 32bit DMA mapping Stefan Richter
2007-02-04 16:06         ` David Moore
2007-02-04 19:25           ` Stefan Richter

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=45ABDB04.1050307@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@steeleye.com \
    --cc=krh@bitplanet.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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