From: Bob McElrath <mcelrath@draal.physics.wisc.edu>
To: linux-kernel@vger.kernel.org
Subject: O_DIRECT as a mount option?
Date: Tue, 25 Sep 2001 12:51:44 -0500 [thread overview]
Message-ID: <20010925125144.D14612@draal.physics.wisc.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
With O_DIRECT (buffer cache bypass open() flag) now in the mainstream
kernel, I wonder if people would be opposed to making a "direct" mount
option, which would open all files on the filesystem with the O_DIRECT
flag, just as there exists a "sync" mount option to perform filesystem
transactions synchronously.
This would allow you to
mount -o direct,sync /dev/hdb1 /mnt/video
And would be useful for things like streaming video applications,
allowing the advantages of O_DIRECT without rewriting every application
you want to use.
Cheers,
-- Bob
Bob McElrath (rsmcelrath@students.wisc.edu)
Univ. of Wisconsin at Madison, Department of Physics
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2001-09-25 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 17:51 Bob McElrath [this message]
2001-09-25 18:55 ` Andrea Arcangeli
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=20010925125144.D14612@draal.physics.wisc.edu \
--to=mcelrath@draal.physics.wisc.edu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®