From: Jeff Moyer <jmoyer@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Dave Kleikamp <dave.kleikamp@oracle.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: O_DIRECT on tmpfs (again)
Date: Fri, 30 Nov 2012 14:39:40 -0500 [thread overview]
Message-ID: <x49ip8mq3r7.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1211291659260.3510@eggly.anvils> (Hugh Dickins's message of "Thu, 29 Nov 2012 17:32:14 -0800 (PST)")
Hugh Dickins <hughd@google.com> writes:
> I've not been entirely convinced that tmpfs needs direct_IO either;
> but your links from back then show a number of people who feel that
> direct_IO had become mainstream enough to deserve the appearance of
> support by tmpfs.
One other thing that occurs to me is that, if we fake O_DIRECT, then
io_submit will block until the I/O is complete. It shouldn't block for
long, sure, but it will still block. I can't say I'm happy about that,
given that many applications mix aio+dio, and will now run into some odd
behaviour when run against tmpfs.
Cheers,
Jeff
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-11-30 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 16:03 O_DIRECT on tmpfs (again) Jeff Moyer
2012-11-28 21:17 ` Hugh Dickins
2012-11-28 21:32 ` Dave Kleikamp
2012-11-29 15:23 ` Jeff Moyer
2012-11-30 1:32 ` Hugh Dickins
2012-11-30 15:01 ` Richard W.M. Jones
2012-11-30 19:39 ` Jeff Moyer [this message]
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=x49ip8mq3r7.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=dave.kleikamp@oracle.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rjones@redhat.com \
/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).