From: Josef Bacik <jbacik@fusionio.com>
To: <lsf-pc@lists.linux-foundation.org>
Cc: <linux-fsdevel@vger.kernel.org>
Subject: [ATTEND] [LSF TOPIC] What to do about O_DIRECT?
Date: Fri, 18 Jan 2013 17:10:07 -0500 [thread overview]
Message-ID: <20130118221007.GA2276@localhost.localdomain> (raw)
Hello,
I'd like to attend this years LSF. I've been doing various file system work for
the last 6 years, most of that with my head down in btrfs.
I'd like to talk about what to do about O_DIRECT. Nobody really owns it and
nobody really _wants_ to own it, and we've all been tacking on our own file
systems optimizations and work arounds to make the generic stuff work. I'm to
the point now where I'm just going to do all the work ourselves inside of btrfs
since we need to have different waiting rules. So the question is do we want to
just rm -f fs/direct-io.c and let everybody do their own thing, or is there some
way we can tease out the actual generic stuff that everybody is going to need to
do and adapt everybody to use that? And then theres the question of what are
the things we want to do in the generic code, do we want to just do the get
pages thing, do we want to still have stuff to build and submit the bios? What
about how AIO interacts with it? And best of all can we convince Zach to do all
of it for us! Thanks,
Josef
next reply other threads:[~2013-01-18 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 22:10 Josef Bacik [this message]
2013-01-18 22:49 ` [ATTEND] [LSF TOPIC] What to do about O_DIRECT? Zach Brown
2013-01-18 23:01 ` Theodore Ts'o
2013-01-20 22:35 ` Dave Chinner
2013-01-21 14:35 ` Josef Bacik
2013-01-22 14:03 ` Jan Kara
2013-01-30 23:16 ` Dave Chinner
2013-01-31 22:41 ` Jan Kara
2013-02-05 21:51 ` Dave Chinner
2013-02-06 0:40 ` Joel Becker
2013-02-06 4:32 ` Kent Overstreet
2013-02-06 17:36 ` Jan Kara
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=20130118221007.GA2276@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-fsdevel@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).