From: Christoph Hellwig <hch@lst.de>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC] Advertise IDE physical block size as 4K
Date: Mon, 4 Jan 2010 09:34:59 +0100 [thread overview]
Message-ID: <20100104083459.GA7660@lst.de> (raw)
In-Reply-To: <68676e00912290539n3f9f9291q54c60e78cdec1611@mail.gmail.com>
On Tue, Dec 29, 2009 at 02:39:38PM +0100, Luca Tettamanti wrote:
> Linux tools put the first partition at sector 63 (512-byte) to retain
> compatibility with Windows;
Well, some of them, and depending on the exact disks. It's all rather
complicated.
> > It has been discussed for hardware disk design with 4k sectors, and
> > somehow there were plans to map sectors so that the Linux partition
> > scheme results in nicely aligned filesystem blocks
>
> Ugh, I hope you're wrong ;-) AFAICS remapping will lead only to
> headaches... Linux does not have any problem with aligned partitions.
Linux doesn't care. As doesn't windows. But performance on mis-aligned
partitions will suck badly - both on 4k sector drives, SSDs or probably
various copy on write layers in virtualization once you hit the worst
case. Fortunately the block topology information present in recent
ATA and SCSI standards allows the storage hardware to tell about the
required alignment, and Linux now has a topology API to expose it, which
is used by the most recent versions of the partitioning tools and
filesystem creation tools.
next parent reply other threads:[~2010-01-04 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1262081278-1858-1-git-send-email-avi@redhat.com>
[not found] ` <20091229132128.GB5736@shareable.org>
[not found] ` <68676e00912290539n3f9f9291q54c60e78cdec1611@mail.gmail.com>
2010-01-04 8:34 ` Christoph Hellwig [this message]
2010-01-04 8:36 ` [Qemu-devel] [PATCH RFC] Advertise IDE physical block size as 4K 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=20100104083459.GA7660@lst.de \
--to=hch@lst.de \
--cc=avi@redhat.com \
--cc=kronos.it@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).