From: Michael Rubin <mrubin@google.com>
To: Mingming <cmm@us.ibm.com>
Cc: Theodore Tso <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
Curt Wohlgemuth <curtw@google.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH RFC] Insure direct IO writes do not use the page cache
Date: Fri, 31 Jul 2009 11:03:45 -0700 [thread overview]
Message-ID: <532480950907311103h695cd79axa01905e33bd3838b@mail.gmail.com> (raw)
In-Reply-To: <532480950907311103s422a70acx25c0ab9c56d1ae31@mail.gmail.com>
On Fri, Jul 31, 2009 at 11:03 AM, Michael Rubin<mrubin@google.com> wrote:
> This will our expectations for DIO on ext4 also.
<sigh>
I meant "This will fulfill our expectations for DIO on ext4 also."
mrubin
next prev parent reply other threads:[~2009-07-31 18:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 0:28 [PATCH RFC] Insure direct IO writes do not use the page cache Curt Wohlgemuth
2009-07-29 16:10 ` Curt Wohlgemuth
2009-07-29 17:18 ` Eric Sandeen
2009-07-29 17:41 ` Eric Sandeen
2009-07-29 19:48 ` Eric Sandeen
2009-07-29 22:17 ` Mingming
2009-07-29 17:47 ` Mingming
2009-07-29 18:10 ` Theodore Tso
2009-07-30 18:30 ` Jan Kara
2009-07-30 18:39 ` Eric Sandeen
2009-07-30 18:44 ` Jan Kara
2009-07-30 19:16 ` Eric Sandeen
2009-07-30 20:33 ` Theodore Tso
2009-07-31 16:10 ` Curt Wohlgemuth
2009-08-01 6:56 ` [PATCH RFC] ext4 direct IO for holes, fallocate Mingming
2009-08-03 16:47 ` Aneesh Kumar K.V
2009-08-03 23:40 ` Mingming
2009-07-31 17:58 ` [PATCH RFC] Insure direct IO writes do not use the page cache Mingming
2009-07-31 18:03 ` Michael Rubin
2009-07-31 18:03 ` Michael Rubin [this message]
2009-08-03 9:36 ` Jan Kara
2009-07-30 11:06 ` Aneesh Kumar K.V
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=532480950907311103h695cd79axa01905e33bd3838b@mail.gmail.com \
--to=mrubin@google.com \
--cc=cmm@us.ibm.com \
--cc=curtw@google.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).