From: Chris Wedgwood <cw@f00f.org>
To: Bruno Diniz de Paula <diniz@cs.rutgers.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_DIRECT foolish question
Date: Wed, 12 Feb 2003 14:07:27 -0800 [thread overview]
Message-ID: <20030212220727.GB12819@f00f.org> (raw)
In-Reply-To: <1045084764.4767.76.camel@urca.rutgers.edu>
On Wed, Feb 12, 2003 at 04:19:24PM -0500, Bruno Diniz de Paula wrote:
> I am trying to use O_DIRECT to read ordinary files and read syscall
> always returns 0, unless when the file size equals the fs block
> size.
Sounds correct.
> Is it true that I can only use O_DIRECT when the size of the file
> written in the inode is a multiple of block size?
You usually can only do O_DIRECT reads/writes in multiples of the
block size (or in some cases multiples of 512-bytes, but I'm not sure
of that code is still about though).
It depends on the filesystem to some extent.
--cw
prev parent reply other threads:[~2003-02-12 21:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 21:19 Bruno Diniz de Paula
2003-02-12 22:03 ` Andrew Morton
2003-02-12 22:29 ` Bruno Diniz de Paula
2003-02-12 22:42 ` Chris Wedgwood
2003-02-12 23:02 ` Bruno Diniz de Paula
2003-02-12 23:22 ` Bruno Diniz de Paula
2003-02-13 1:46 ` Randy.Dunlap
2003-02-12 23:24 ` Chris Wedgwood
2003-02-12 23:33 ` Bruno Diniz de Paula
2003-02-12 23:38 ` Chris Wedgwood
2003-02-12 23:49 ` Bruno Diniz de Paula
2003-02-12 23:51 ` Chris Wedgwood
[not found] ` <1045094589.4767.106.camel@urca.rutgers.edu>
[not found] ` <20030213001302.GA13833@f00f.org>
2003-02-13 0:36 ` Bruno Diniz de Paula
2003-02-13 5:12 ` Andrew Morton
2003-02-13 15:22 ` Bruno Diniz de Paula
2003-02-13 17:31 ` Andrew Morton
2003-02-13 22:45 ` Bruno Diniz de Paula
2003-02-12 23:33 ` Chris Wedgwood
2003-02-12 22:07 ` Chris Wedgwood [this message]
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=20030212220727.GB12819@f00f.org \
--to=cw@f00f.org \
--cc=diniz@cs.rutgers.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®