From: jim owens <owens6336@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Chris Mason <chris.mason@oracle.com>,
Josef Bacik <josef@redhat.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH V2] Btrfs: Full direct I/O and AIO read implementation.
Date: Mon, 15 Feb 2010 17:26:34 -0500 [thread overview]
Message-ID: <4B79CA1A.6070705@gmail.com> (raw)
In-Reply-To: <20100215215823.GA3763@infradead.org>
Christoph Hellwig wrote:
> On Mon, Feb 15, 2010 at 11:42:55AM -0500, Chris Mason wrote:
>> We can record the smallest alignment while scanning the devices and just
>> use that. In general 4K is good enough, although some other database
>> company might be more worried about smaller numbers.
>
> How is access at 512 byte granularity supposed to work? With 4k logical
> sector drives that will require a manual read-modify write cycle in
> the direct I/O code, which is counter the intentions.
My understanding is the current 4k drives normally operate in
512 byte read/write access mode unless you set them to run
as 4k only.
In 512 byte mode, they buffer internally on writes. It is probably
just as safe as any other drive on a power hit, as in anything may
be trash.
btrfs read of 512 byte boundaries is safe because we only write
in 4k boundaries (hopefully we can detect and align on the drive).
jim
next prev parent reply other threads:[~2010-02-15 22:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 18:53 [PATCH V2] Btrfs: Full direct I/O and AIO read implementation jim owens
2010-02-12 19:28 ` Josef Bacik
2010-02-14 1:30 ` jim owens
2010-02-15 16:42 ` Chris Mason
2010-02-15 19:18 ` jim owens
2010-02-16 16:01 ` Chris Mason
2010-02-16 17:09 ` jim owens
2010-02-15 21:58 ` Christoph Hellwig
2010-02-15 22:26 ` jim owens [this message]
2010-02-15 22:32 ` Christoph Hellwig
2010-02-15 22:40 ` jim owens
2010-02-16 15:49 ` Chris Mason
2010-02-15 22:01 ` rk
2010-02-15 22:31 ` jim owens
2010-02-16 19:28 ` jim owens
2010-02-16 19:39 ` Josef Bacik
2010-03-03 18:54 ` jim owens
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=4B79CA1A.6070705@gmail.com \
--to=owens6336@gmail.com \
--cc=chris.mason@oracle.com \
--cc=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.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