From: Andreas Dilger <adilger@clusterfs.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: O_DIRECT support in ext3?
Date: Tue, 13 Aug 2002 11:27:05 -0600 [thread overview]
Message-ID: <20020813172705.GG9642@clusterfs.com> (raw)
In-Reply-To: <200208131548.36267.roy@karlsbakk.net>
On Aug 13, 2002 15:48 +0200, Roy Sigurd Karlsbakk wrote:
> playing around with O_DIRECT, I really _can't_ make it work on ext3?
>
> why is this?
Because O_DIRECT needs a specific o_direct I/O method that has not yet
been written for ext3. I believe only ext2 and reiserfs support it
right now. I will eventually need to add support for this, but it is
not yet high on my list of priorities. Maybe someone else will beat
me to it.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-08-13 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 13:48 O_DIRECT support in ext3? Roy Sigurd Karlsbakk
2002-08-13 17:27 ` Andreas Dilger [this message]
2002-08-13 21:00 ` Andrew Morton
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=20020813172705.GG9642@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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