From: Chris Mason <chris.mason@fusionio.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 0/2] Support for atomic IOs
Date: Fri, 1 Nov 2013 17:27:04 -0400 [thread overview]
Message-ID: <20131101212704.10239.73920@localhost.localdomain> (raw)
Hi everyone,
I'm still testing this (especially to look for unrelated regressions in
MD and DM), but wanted to send it out for comments.
These two patches implement support for atomic IOs down to the hardware.
The basic idea is that we give a list of bios to the storage and even
if they are discontiguous the hardware promises to complete them as a
single atomic unit.
The first user for this is O_DIRECT, especially for mysql based
databases. O_ATOMIC | O_DIRECT allows mysql and friends to disable
double buffering. This cuts their write IO in half, making them
roughly 2x more flash friendly.
The patches are on top of Jens' current blk-mq/core tree. Jens
also has chaining patches from Kent, but he is chaining bios likely to
be sent to separate devices, while I'm chaining bios that must
(currently) be sent to the same device as a group.
As far as I can tell, there isn't much overlap in our targets or
methods, but I'd like to eventually merge the ideas together.
-chris
next reply other threads:[~2013-11-01 21:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 21:27 Chris Mason [this message]
2013-11-01 21:28 ` [PATCH 1/2] block: Add support for atomic writes Chris Mason
2013-11-01 21:47 ` Shaohua Li
2013-11-05 17:43 ` Jeff Moyer
2013-11-07 13:52 ` Chris Mason
2013-11-07 15:43 ` Jeff Moyer
2013-11-07 15:55 ` Chris Mason
2013-11-07 16:14 ` Jeff Moyer
2013-11-07 16:52 ` Chris Mason
2013-11-13 23:59 ` Dave Chinner
2013-11-12 15:11 ` Matthew Wilcox
2013-11-13 20:44 ` Chris Mason
2013-11-13 20:53 ` Howard Chu
2013-11-13 21:35 ` Matthew Wilcox
2013-11-01 21:29 ` [PATCH 2/3] fs: Add O_ATOMIC support to direct IO Chris Mason
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=20131101212704.10239.73920@localhost.localdomain \
--to=chris.mason@fusionio.com \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).