From: Arjan van de Ven <arjan@infradead.org>
To: "Hanson, Jonathan M" <jonathan.m.hanson@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Using O_DIRECT for file writing in a kernel module
Date: Fri, 11 Feb 2005 22:32:44 -0500 [thread overview]
Message-ID: <1108179164.4055.21.camel@localhost.localdomain> (raw)
In-Reply-To: <C863B68032DED14E8EBA9F71EB8FE4C20639287E@azsmsx406>
On Fri, 2005-02-11 at 17:58 -0700, Hanson, Jonathan M wrote:
> I'm trying to write to a file with the O_DIRECT flag from a
> kernel module in a 2.4 series of kernel on x86 hardware. I've learned
> that the O_DIRECT flag requires that the amount of data written and the
> file offset pointer must be multiples of the underlying "block size."
ehhh why are you writing to a file from a kernel module? That's
generally considered a really bad idea....
next prev parent reply other threads:[~2005-02-12 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 0:58 Hanson, Jonathan M
2005-02-12 3:32 ` Arjan van de Ven [this message]
2005-02-12 14:26 Hanson, Jonathan M
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=1108179164.4055.21.camel@localhost.localdomain \
--to=arjan@infradead.org \
--cc=jonathan.m.hanson@intel.com \
--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®