linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Smietanowski <stesmi@stesmi.com>
To: Saswat Praharaj <saswat@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: read vs write
Date: Mon, 25 Jul 2005 14:36:22 +0200	[thread overview]
Message-ID: <42E4DCC6.7010302@stesmi.com> (raw)
In-Reply-To: <d15adc960507250440510efd58@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Saswat Praharaj wrote:
> 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 ]

Yes, burst is transfer speed not speed from the platter.

The drive has a cache (2MB). From that cache you can transfer
at 100MB/s, not from the platter sadly enough. Even those 10kRPM
drives don't do 100.

So road == cable == from cache in a sense (assuming the cache can
do 100MB/s).
T-Ford = platter.

I wish it was different but it's not.

I mean, a SATAII-300 - do you honestly believe you can read and write
att 300MB/s to that drive? To/From Cache : maybe. Platter : No way.

But if you read the same data 10 times in a row (size=1MB let's say)
then yes, you should be seeing 100MB/s or somewhere close depending on
where your controller is, how saturated the bus is, etc.

// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFC5NzGBrn2kJu9P78RAikFAJ0Tg073q3hsBb6bG9ucwOqYLaxBuQCfQWqk
gYjK8WJ/at4uNJhks+uh3RA=
=cNWZ
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2005-07-25 12:30 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
2005-07-25 12:34     ` Tyler
2005-07-25 12:36     ` Stefan Smietanowski [this message]

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=42E4DCC6.7010302@stesmi.com \
    --to=stesmi@stesmi.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=saswat@gmail.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).