From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: bugme-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 10846] New: Slow write on LSISAS1068E (SAS6/iR) on kernel >= 2.6.22
Date: Mon, 02 Jun 2008 10:11:03 -0500 [thread overview]
Message-ID: <1212419463.3369.10.camel@localhost.localdomain> (raw)
In-Reply-To: <bug-10846-11613@http.bugzilla.kernel.org/>
On Mon, 2008-06-02 at 07:57 -0700, bugme-daemon@bugzilla.kernel.org
wrote:
> Very easy: We also check for an untar of the kernel (5x slower)
> debian-test:~# dd if=/dev/zero of=/root/test.cdrom bs=10k count=60000
> 60000+0 enregistrements lus
> 60000+0 enregistrements écrits
> 614400000 octets (614 MB) copiés, 1,17602 seconde, 522 MB/s
> debian-test:~# uname -a
> Linux debian-test.pr.univmed.fr 2.6.19.7 #1 SMP Fri May 30 15:55:50
> CEST 2008
> i686 GNU/Linux
>
> debian:~# dd if=/dev/zero of=test.cdrom bs=10k count=60000
> 60000+0 records in
> 60000+0 records out
> 614400000 bytes (614 MB) copied, 7.51225 seconds, 81.8 MB/s
> debian:~# uname -a
> Linux debian 2.6.22-4-vserver-686 #1 SMP Tue Feb 12 22:02:04 UTC 2008
> i686
> GNU/Linux
What exactly is test.cdrom on? A single disk? If so, then your first
result is definitely bogus. The maximum bandwidth of a single SAS link
is 300 MB/s, so it looks like the kernel is either caching the write or
has timing issues. For a direct to platter speed, the data sheet for
your drive gives 55-89MB/s, so I'd say 81.8 is well within the range.
James
--
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:[~2008-06-02 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 14:57 [Bug 10846] New: Slow write on LSISAS1068E (SAS6/iR) on kernel >= 2.6.22 bugme-daemon
2008-06-02 15:11 ` James Bottomley [this message]
2008-06-02 15:11 ` [Bug 10846] " bugme-daemon
2008-06-02 21:09 ` bugme-daemon
2008-06-03 7:00 ` bugme-daemon
2008-06-03 14:11 ` James Bottomley
2008-06-03 14:12 ` bugme-daemon
2008-06-03 16:09 ` bugme-daemon
2008-06-03 20:15 ` James Bottomley
2008-06-03 19:21 ` bugme-daemon
2008-06-03 20:15 ` bugme-daemon
2008-06-04 15:22 ` bugme-daemon
2008-06-13 7:52 ` bugme-daemon
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=1212419463.3369.10.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=bugme-daemon@bugzilla.kernel.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