From: Doron Shoham <dorons@Voltaire.COM>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: using direct IO with sgp_dd
Date: Tue, 11 Mar 2008 11:12:40 +0200 [thread overview]
Message-ID: <47D64D08.6070601@Voltaire.COM> (raw)
In-Reply-To: <e2e108260803110150g453c790bu3a21537b5eaf762d@mail.gmail.com>
Bart Van Assche wrote:
> On Tue, Mar 11, 2008 at 8:40 AM, Doron Shoham <dorons@voltaire.com> wrote:
>> sgp_dd if=/dev/sg1 of=/dev/null bs=512 bpt=128 thr=8 time=1 count=5M dio=1
>> time to transfer data was 2.236290 secs, 1200.36 MB/sec
>> 5242880+0 records in
>> 5242880+0 records out
>> Direct IO requested but incomplete 40960 times
>>
>> What does it mean "Direct IO requested but incomplete 40960 times"?
>> And what could be the reason for this?
>
> The man page of sgp_dd states that the parameter specified to bs must
> be the block size of the physical device. You can query the block size
> of a SCSI device with e.g. the scsi_readcap command:
>
> $ scsi_readcap /dev/sda
> sg_readcap /dev/sda
> Read Capacity results:
> Last logical block address=625142447 (0x2542eaaf), Number of blocks=625142448
> Logical block length=512 bytes
> Hence:
> Device size: 320072933376 bytes, 305245.3 MiB, 320.07 GB
>
> Bart.
Hi,
sg_readcap /dev/sdb
Read Capacity results:
Last block address=3221225471 (0xbfffffff), Number of blocks=3221225472
Block size=512 bytes
Hence:
Device size: 1649267441664 bytes, 1572864.0 MiB, 1649.27 GB
The block size is 512 as I used in the sgp_dd command.
The problem is just when using dio=1, without it it works ok.
Thanks,
Doron
next prev parent reply other threads:[~2008-03-11 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 7:40 using direct IO with sgp_dd Doron Shoham
2008-03-11 8:50 ` Bart Van Assche
2008-03-11 9:12 ` Doron Shoham [this message]
2008-03-12 22:46 ` Douglas Gilbert
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=47D64D08.6070601@Voltaire.COM \
--to=dorons@voltaire.com \
--cc=bart.vanassche@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.