From: Stan Hoeppner <stan@hardwarefreak.com>
To: Zheng Da <zhengda1936@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: concurrent direct IO write in xfs
Date: Mon, 23 Jan 2012 18:34:08 -0600 [thread overview]
Message-ID: <4F1DFC80.1040204@hardwarefreak.com> (raw)
In-Reply-To: <CAFLer81GWSCCCMppU=2dE+5KKqD-hYVKAA0hz9n-CBbxAs_xfw@mail.gmail.com>
On 1/23/2012 2:51 PM, Zheng Da wrote:
> tmpfs doesn't support direct IO.
Of course not. tmpfs resides entirely within the page cache (or some of
it in swap). The whole point of direct IO is to bypass the page cache,
transferring data directly between user space memory and the storage
device. As tmpfs is built entirely within the page cache, direct IO is
obviously impossible. And it's also obviously unnecessary.
Yes, you will need to rewrite your application to use tmpfs as direct IO
calls won't work. This is something you obviously would rather not do.
Which brings us back to Dave's question, which you have not answered:
What exactly is the purpose of your program? What does it aim to
accomplish? Is it for a database application? A word processor? Or
simply a filesystem tester? What do _you_ aim to accomplish with this
programming effort?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-24 0:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 0:01 concurrent direct IO write in xfs Zheng Da
2012-01-16 17:48 ` Christoph Hellwig
2012-01-16 19:44 ` Zheng Da
2012-01-16 23:25 ` Dave Chinner
2012-01-17 19:19 ` Zheng Da
2012-01-20 8:53 ` Linda Walsh
2012-01-20 15:07 ` Zheng Da
2012-01-23 5:11 ` Dave Chinner
2012-01-23 19:34 ` Zheng Da
2012-01-23 20:51 ` Zheng Da
2012-01-24 0:34 ` Stan Hoeppner [this message]
2012-01-24 1:40 ` Zheng Da
2012-01-24 3:54 ` Dave Chinner
2012-01-25 21:20 ` Zheng Da
2012-01-25 22:25 ` Dave Chinner
2012-02-09 6:09 ` Dave Chinner
2012-02-09 6:44 ` Zheng Da
2012-02-13 17:48 ` Christoph Hellwig
2012-02-13 23:07 ` Dave Chinner
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=4F1DFC80.1040204@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
--cc=zhengda1936@gmail.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