From: Theodore Ts'o <tytso@mit.edu>
To: Josef Bacik <jbacik@fusionio.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ATTEND] [LSF TOPIC] What to do about O_DIRECT?
Date: Fri, 18 Jan 2013 18:01:28 -0500 [thread overview]
Message-ID: <20130118230128.GA15758@thunk.org> (raw)
In-Reply-To: <20130118221007.GA2276@localhost.localdomain>
.... and can we get rid of this horrible hack where we have this
bastardized use of a struct buffer_head which is allocated on the
stack, which has nothing really to do with a buffer head, and is all
about the fact that no one wants to change the function signature for
get_block_t?
- Ted
next prev parent reply other threads:[~2013-01-18 23:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 22:10 [ATTEND] [LSF TOPIC] What to do about O_DIRECT? Josef Bacik
2013-01-18 22:49 ` Zach Brown
2013-01-18 23:01 ` Theodore Ts'o [this message]
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=20130118230128.GA15758@thunk.org \
--to=tytso@mit.edu \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.