From: Reza Roboubi <reza@earthdetails.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: torvalds@linux-foundation.org
Subject: O_DIRECT, fdatasync_area, mwrite
Date: Thu, 21 Jun 2007 12:02:28 -0700 [thread overview]
Message-ID: <467ACB44.50209@earthdetails.com> (raw)
Linus Torvalds:
> I suspect that this is about a few hundred lines of code (and a lot of
> testing). And you can emulate O_DIRECT behavior with it, along with
> splice (only for page-cache entities, though), and a lot of other
> off-by-one uses.
( http://lwn.net/2002/0516/a/lt-async.php3 )
I have often read this message and wondered why no one has implemented
it yet. We would love to have such clean features instead of O_DIRECT.
At this very moment it's a bit hard for us to do this(given a
prerequisites learning curve amongst other factors.) We may at some
point do it and I'd love to contribute. What _are_ the issues with it,
and is there a technical reason it hasn't been implemented yet by anybody?
Further, is O_DIRECT to raw partition also unclean?
Thanks.
Reza.
--
Reza Roboubi
Chief Technical Officer
http://www.EarthDetails.com
next reply other threads:[~2007-06-21 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 19:02 Reza Roboubi [this message]
2007-06-22 5:43 ` O_DIRECT, fdatasync_area, mwrite Reza Roboubi
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=467ACB44.50209@earthdetails.com \
--to=reza@earthdetails.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@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.