From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Kristian Høgsberg" <krh@bitplanet.net>
Cc: 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 21:02:14 +0100 (CET) [thread overview]
Message-ID: <tkrat.8dad811bf4dbb360@s5r6.in-berlin.de> (raw)
In-Reply-To: <59ad55d30701151139w6176e785g53404d7b3a42ce6e@mail.gmail.com>
On 15 Jan, Kristian Høgsberg wrote:
> On 1/14/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> 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.
SBP-2 clause 5.2. It's also in SBP-3 even though there is no obvious
benefit for this rule.
> 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.
Yes, after the discussion this occurred to me too but my energy reserves
were already too low to wrap this up.
> 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.
Douglas has a very informative text on this:
http://sg.torque.net/sg/sg_io.html#mozTocId154063
| [...] since lk 2.6.16 another limit comes into play: the
| MAX_SEGMENT_SIZE define which is set to 64 KB. MAX_SEGMENT_SIZE is a
| default and can be overridden by the LLD calling
| blk_queue_max_segment_size().
Looks like we can yank out some cruft off sbp2.
--
Stefan Richter
-=====-=-=== ---= -====
http://arcgraph.de/sr/
-
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
next prev parent reply other threads:[~2007-01-15 20:02 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
2007-01-15 20:02 ` Stefan Richter [this message]
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=tkrat.8dad811bf4dbb360@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@steeleye.com \
--cc=krh@bitplanet.net \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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