From: Christoph Hellwig <hch@infradead.org>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: NewStore update
Date: Sun, 22 Feb 2015 07:51:53 -0800 [thread overview]
Message-ID: <20150222155153.GA19387@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1502210952130.14643@cobra.newdream.net>
On Sat, Feb 21, 2015 at 09:53:45AM -0800, Sage Weil wrote:
> Ah, thanks. I guess in the buffered case though we won't block normally
> anyway (unless we've hit the bdi dirty threshold). So it's probably
> either aio direct or buffered write + aio fsync, depending on the cache
> hints?
buffered I/O will also block on:
- acquiring i_mutex (do you plan on having parallel writers to the same
file?)
- reading in the page for read-modify-write cycles
- waiting for writeback to finish for a previous write to the page
In adition to all the other ways even O_DIRECT aio could block (most
importantly block allocation)
I have a hacked prototype to do non-blocking writes similar to the
non-blocking reads we've been discussion on fsdevel for the last half
year.
prev parent reply other threads:[~2015-02-22 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 23:50 NewStore update Sage Weil
2015-02-20 10:01 ` Haomai Wang
2015-02-20 15:00 ` Sage Weil
2015-02-20 16:16 ` Haomai Wang
2015-02-20 16:35 ` Mark Nelson
2015-02-21 15:50 ` Christoph Hellwig
2015-02-21 17:53 ` Sage Weil
2015-02-22 15:51 ` Christoph Hellwig [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=20150222155153.GA19387@infradead.org \
--to=hch@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.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