From: Kent Overstreet <kmo@daterainc.com>
To: lsf-pc@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: [LSF/MM TOPIC] [ATTEND] Direct IO
Date: Thu, 16 Jan 2014 14:28:42 -0800 [thread overview]
Message-ID: <20140116222842.GQ9037@kmo> (raw)
Hi, I'd like to discuss the current state and future direction of the DIO code.
I and others have been kicking around the idea for some time now of reworking
direct IO at the filesystem level in terms of bios; this will radically simplify
fs/direct-IO.c, and solve some other longstanding issues, like double usage of
the page cache by the loopback device - the goal will be for things like loop to
just be able to submit bios to the filesystem code.
Immutable biovecs are now almost upstream, which was a major prereq; this helps
enables a DIO rewrite that basically pushes bios up a layer. Soon, we'll need to
start reworking vfs interfaces, and input from the filesystem developers
(especially btrfs) will be necessary there.
reply other threads:[~2014-01-16 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140116222842.GQ9037@kmo \
--to=kmo@daterainc.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).