From: Douglas Gilbert <dougg@torque.net>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Jeff Garzik <jeff@garzik.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi updates for post 2.6.18
Date: Thu, 05 Oct 2006 19:34:17 -0400 [thread overview]
Message-ID: <45259679.7050804@torque.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0610052129020.6619@poirot.grange>
Guennadi Liakhovetski wrote:
> On Thu, 5 Oct 2006, Jeff Garzik wrote:
>
>> Guennadi Liakhovetski wrote:
>>> On Wed, 4 Oct 2006, James Bottomley wrote:
>>>
>>>> This is (hopefully) my final batch of updates before we go -rc1. It's
>>>> mainly code cleanups, some driver updates and the new qla4xxx iScsi
>>>> driver.
>>> James, is there a reason why you didn't include this one:
>>>
>>> http://marc.theaimsgroup.com/?l=linux-scsi&m=115974328128341&w=2
>>>
>>> Do you think it can cause problems?
>> It would be nice to get it tested, based on your "don't know if it works
>> though" comment...
>
> Sure, it WOULD be nice, but I don't know how. The "don't know" refers to
> the case 16MB block size, my tape supports only 16MB - 1 byte (according
> to st report). Is there a way to test various block sizes with CDs /
> hard-disks / ZIP / scanners?
> Would something with sg_dd work?
Interesting challenge.
In lk 2.6.19-rc1 with /dev/sda and
/dev/sg0 the same SCSI disk I can get close:
[root@sas parameters]# cd /sys/block/sda/queue/
[root@sas queue]# echo 32767 > max_sectors_kb
[root@sas queue]# cd /sys/module/sg/parameters/
[root@sas parameters]# echo 131072 > scatter_elem_sz
[root@sas parameters]# sg_dd if=/dev/sg0 of=/dev/null bs=512 bpt=32640 count=32k verbose=3
>> Input file type: SCSI generic (sg) device
open input(sg_io), flags=0x800
inquiry cdb: 12 00 00 00 24 00
/dev/sg0: SEAGATE ST336754SS 0003 [pdt=0]
>> Output file type: null device
read cdb: 28 00 00 00 00 00 00 7f 80 00
duration=180 ms
read cdb: 28 00 00 00 7f 80 00 00 80 00
duration=4 ms
32768+0 records in
32768+0 records out
So I got within 128 (512 byte) sectors of a 16 MB transfer
on a single command. Hmm.
This is with a adaptec 48300 HBA with the aic94xx driver
(take your pick which one).
Looks like
> it must be only sector size. Can I low-level format a disk with 16M
> sector?:-)
No usually. Some SCSI disk can be formatted up to 528
byte sectors but that is a long way short.
> Another possibility is to limit the block size at 8MB - I can test that.
The sg driver gets around that in lk 2.6.19-rc1
Doug Gilbert
next prev parent reply other threads:[~2006-10-05 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 21:01 [GIT PATCH] scsi updates for post 2.6.18 James Bottomley
2006-10-05 19:11 ` Guennadi Liakhovetski
2006-10-05 19:16 ` Jeff Garzik
2006-10-05 19:56 ` Guennadi Liakhovetski
2006-10-05 20:12 ` Jeff Garzik
2006-10-05 22:12 ` Guennadi Liakhovetski
2006-10-05 23:34 ` Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-24 2:37 James Bottomley
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=45259679.7050804@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=g.liakhovetski@gmx.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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