From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Harper <james.harper@bendigoit.com.au>
Cc: Joseph Glanville <joseph.glanville@orionvm.com.au>,
Keir Fraser <keir.xen@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: bug when using 4K sectors?
Date: Sun, 16 Sep 2012 17:07:37 +0100 [thread overview]
Message-ID: <20120916170737.3c8f7e9e@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29B980EB@BITCOM1.int.sbss.com.au>
> > So knowing the block size isn't the whole story.
> >
>
> Are you saying that Xen and/or Linux needs to worry about a user setting up a poorly aligned filesystem to pass to a VM? Seems simpler just to set things up right in the first place.
That assumes things like a file system and the existing layout being
correct. Plus you also have to set the thing up which means you have to
know about such stuff.
For file systems Linux itself does indeed take the approach of "so
partition sensibly" because in the fs case it's really hard if not
impossible to do a good job any other way.
For raw devices and things like databases wanting atomicity of block
writes however its quite different and you need to be aware of the
alignments.
Alan
prev parent reply other threads:[~2012-09-16 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 14:12 bug when using 4K sectors? James Harper
2012-09-05 20:29 ` Konrad Rzeszutek Wilk
2012-09-05 23:56 ` James Harper
2012-09-06 10:58 ` Konrad Rzeszutek Wilk
2012-09-16 7:00 ` Joseph Glanville
2012-09-16 8:31 ` Keir Fraser
2012-09-16 9:00 ` Joseph Glanville
2012-09-16 10:37 ` James Harper
2012-09-16 11:18 ` Keir Fraser
2012-09-16 11:21 ` James Harper
2012-09-16 11:27 ` Alan Cox
2012-09-16 11:50 ` James Harper
2012-09-16 16:07 ` Alan Cox [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=20120916170737.3c8f7e9e@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=james.harper@bendigoit.com.au \
--cc=joseph.glanville@orionvm.com.au \
--cc=keir.xen@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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).