From: Andreas Dilger <adilger@clusterfs.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Ric Wheeler <ric@emc.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: impact of 4k sector size on the IO & FS stack
Date: Tue, 13 Mar 2007 01:11:44 -0400 [thread overview]
Message-ID: <20070313051144.GI5266@schatzie.adilger.int> (raw)
In-Reply-To: <45F56318.9030505@garzik.org>
On Mar 12, 2007 10:26 -0400, Jeff Garzik wrote:
> In my own experiments on my own Fedora workstation, ~66% of IOs in Linux
> start on an odd sector, and ~33% started on even-numbered sectors. For
> a 1K-sector drive with 'odd' alignment, the configuration Microsoft will
> likely want, that means the majority of disk transactions will avoid a
> RMW cycle, but a still-numerous minority will not.
Isn't that purely an artifact of the DOS partition table alignment, possibly
skewed by the fact that most of your IO is on partition 1 & 3? Hard to
believe this because of the nice even numbers though.
Since ext3 has at least 1kB blocksize and defaults to 4kB blocksize with
most modern disks because they are > 500MB in size, you should never
have misaligned writes generated by the filesystem itself.
> I did not test
> transfer length, to see how many transfers /ended/ on an odd sector,
> thus determining how many RMW cycles the tail of an average I/O requires.
I'd guess a vast majority of IO will have the end similarly misaligned as
the start. Very little filesystem IO is 512 bytes, possibly excluding XFS
in an unusual mode.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-03-13 5:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 22:51 impact of 4k sector size on the IO & FS stack Ric Wheeler
2007-03-11 23:14 ` Jan Engelhardt
2007-03-12 2:45 ` Ric Wheeler
2007-03-12 3:27 ` Jan Engelhardt
2007-03-12 3:46 ` Andreas Dilger
2007-03-12 12:17 ` Alan Cox
2007-03-12 14:41 ` Jeff Garzik
2007-03-12 14:36 ` Jeff Garzik
2007-03-12 15:45 ` Alan Cox
2007-03-12 18:31 ` Bryan Henderson
2007-03-12 18:37 ` Sergei Shtylyov
2007-03-12 20:52 ` Bryan Henderson
2007-03-12 19:16 ` Douglas Gilbert
2007-03-12 19:28 ` Jeff Garzik
2007-03-12 0:02 ` Alan Cox
2007-03-12 0:44 ` Jeff Garzik
2007-03-12 2:37 ` Ric Wheeler
2007-03-12 12:24 ` Alan Cox
2007-03-12 13:32 ` Ric Wheeler
2007-03-12 15:21 ` Douglas Gilbert
2007-03-12 16:08 ` Martin K. Petersen
2007-03-12 14:26 ` Jeff Garzik
2007-03-13 5:11 ` Andreas Dilger [this message]
2007-03-13 6:34 ` Chris Wedgwood
2007-03-12 2:41 ` Ric Wheeler
2007-03-12 8:18 ` Christoph Hellwig
2007-03-12 14:40 ` James Bottomley
2007-03-12 14:45 ` Jeff Garzik
2007-03-12 14:57 ` Christoph Hellwig
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=20070313051144.GI5266@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ric@emc.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).