From: Saswat Praharaj <saswat@gmail.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: read vs write
Date: Mon, 25 Jul 2005 17:10:22 +0530 [thread overview]
Message-ID: <d15adc960507250440510efd58@mail.gmail.com> (raw)
In-Reply-To: <42E4BFC1.7070905@stesmi.com>
yups I meant MBps ..thanks for correcting me .
However, I dont agree with your ford/road example.
I just checked the product specification of STA340016A (seagate) .
Here is what they claim :
[ This manual describes the functional, mechanical and interface specifi-
cations for the ST380021A, ST360021A, ST340016A and ST320011A.
These drives provide the following key features:
· 7,200-RPM spindle speed and 2-Mbyte buffer combine for superior
desktop performance
· High instantaneous (burst) data-transfer rates (up to 100 Mbytes per
second) using Ultra DMA mode 5 ]
I have found average seek time is little faster (around 1ms) for read
than write.
Still that doesn't justify the write speed of 15-20 MBps and 55-60
MBps for read.
Can anyone help me understading how/why write is different than read.
Thanks and Regards,
Saswat
On 7/25/05, Stefan Smietanowski <stesmi@stesmi.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Saswat.
>
> > Moreover, I am wondering if I could achieve the 100Mbps read speed as
> > claimed by different vendors.For me , It should ideally be 100 Mbps as
> > I am using a 80 conductor cable and UDMA 5.Why then I am getting 58
> > Mbps max . .
>
> If you mean Mbps then you are already above it. 100Mbps = 12.5MB/s
> give or take and both speeds are above that.
> I guess you probably mean 100MB/s though and that is only what
> the cable can take.
>
> If you take a T-ford onto the highway - can you go 130Km/h in it?
>
> No, the road is rated at 130Km/s but the car can't go that fast.
>
> Same here, the standard says you can transfer 100MB/s over the cable
> but the disk isn't fast enough to be able to transfer that fast.
>
> // Stefan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
>
> iD8DBQFC5L/BBrn2kJu9P78RAkXKAJ4vc/xQ0Z8mA1ddo79+wC6NCFe5VACgl+j+
> ceP+as8dx0uZs2W6xaYiMVc=
> =Of1/
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2005-07-25 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 10:14 read vs write Saswat Praharaj
2005-07-25 10:32 ` Stefan Smietanowski
2005-07-25 11:40 ` Saswat Praharaj [this message]
2005-07-25 12:34 ` Tyler
2005-07-25 12:36 ` Stefan Smietanowski
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=d15adc960507250440510efd58@mail.gmail.com \
--to=saswat@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=stesmi@stesmi.com \
/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;
as well as URLs for NNTP newsgroup(s).