From: Brian Beattie <beattie@beattie-home.net>
To: linux-fsdevel@vger.kernel.org
Subject: direct i/o on 2.4
Date: 21 Oct 2003 13:44:08 -0400 [thread overview]
Message-ID: <1066758249.1293.7.camel@kokopelli> (raw)
can anybody point me at information regarding direct io on a recent 2.4
kernel and how this works (or does not work) with XFS and LVM.
--
Brian Beattie | Experienced kernel hacker/embedded systems
beattie@beattie-home.net | programmer, direct or contract, short or
www.beattie-home.net | long term, available immediately.
"Honor isn't about making the right choices.
It's about dealing with the consequences." -- Midori Koto
reply other threads:[~2003-10-21 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1066758249.1293.7.camel@kokopelli \
--to=beattie@beattie-home.net \
--cc=linux-fsdevel@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