mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Eric D. Mudama" <edmudama@mail.bounceswoosh.org>,
	Timothy Miller <miller@techsource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: File system performance, hardware performance, ext3, 3ware RAID1, etc.
Date: Fri, 13 Feb 2004 23:45:24 +0100	[thread overview]
Message-ID: <20040213224524.GB13937@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.58.0402131146040.2144@home.osdl.org>

On Fri, Feb 13, 2004 at 11:55:16AM -0800, Linus Torvalds wrote:
 
> > the absolute worst-case write performance should be the same as read
> > performance.
> 
> That is only true if the disk block-size is smaller than the IO blocksize. 
> Can somebody fill me in on what modern disks do, especially the 
> high-density ones?

This is purely hypothetical, but perhaps write-precompensation or the signal
intensity or shape in the head implies to write at "safer" frequencies ? we're
speaking about hundreds of megahertz, and I've always wondered what the signal
looks like when it reaches the head.

Cheers,
Willy


  parent reply	other threads:[~2004-02-13 22:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 23:32 Timothy Miller
2004-02-13  5:53 ` Willy Tarreau
2004-02-13 19:19   ` Timothy Miller
2004-02-13 22:39     ` Willy Tarreau
2004-02-13 23:14       ` Timothy Miller
2004-02-13 19:30   ` Eric D. Mudama
2004-02-13 19:55     ` Linus Torvalds
2004-02-13 20:44       ` John Bradford
2004-02-13 22:45       ` Willy Tarreau [this message]
2004-02-13 12:23 Daniel Blueman
2004-02-13 14:27 ` Jamie Lokier
2004-02-13 14:44   ` Daniel Blueman
2004-02-13 16:15     ` Bartlomiej Zolnierkiewicz
2004-02-13 22:56 ` Timothy Miller
2004-02-14 18:16 Walt H
2004-02-16 17:53 ` Timothy Miller

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=20040213224524.GB13937@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=edmudama@mail.bounceswoosh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.com \
    --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

all inboxes | Powered by JetHome®