From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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: Sun, 11 Mar 2007 20:44:24 -0400 [thread overview]
Message-ID: <45F4A268.3000405@garzik.org> (raw)
In-Reply-To: <20070312000253.20eab1a3@lxorguk.ukuu.org.uk>
Alan Cox wrote:
> I would be interested to know what the disk vendors intend to use as
> their strategy when (with ATA) they have a 512 byte write from an older
> file system/setup into a 4K block. The case where errors magically appear
Well, you have logical and physical sector size changes.
First generation of 1K sector drives will continue to use the same
512-byte ATA sector size you are familiar with. A single 512-byte write
will cause the drive to perform a read-modify-write cycle. This
configuration is physical 1K sector, logical 512b sector.
A future configuration will change the logical ATA interface away from
512-byte sectors to 1K or 4K. Here, it is impossible to read a quantity
smaller than 1K or 4K, whatever the sector size is.
Jeff
next prev parent reply other threads:[~2007-03-12 0:44 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 [this message]
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
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=45F4A268.3000405@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.