From: Jan Blunck <j.blunck@tu-harburg.de>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RESEND] don't allow sys_readahead() on files opened with O_DIRECT
Date: Thu, 25 Aug 2005 14:13:22 +0200 [thread overview]
Message-ID: <430DB5E2.9060103@tu-harburg.de> (raw)
In-Reply-To: <20050825012440.66b61cca.akpm@osdl.org>
Andrew Morton schrieb:
>
> a) It doesn't hurt, it's just a bit of a silly thing to do.
IMO it may hurt the performance.
>
> b) posix_fadvise(POSIX_FADV_WILLNEED) should get the same treatment (and
> it's the preferred way of doing readahead).
Yes, of course.
>
> c) O_DIRECT fd's should, as much as possible, offer the same ABI as
> buffered fd's.
Hmm, with XIP fd's we agreed on the following behavior: fadvise() and
madvise() just return without reading anything to the page cache. Since
XIP fd's are similar to O_DIRECT fd's their behavior should be similar,
too. If we don't honor the advises we might also ignore the syscall. At
least redhat's readahead is using them.
Maybe we should agree on one behavior that makes sense. And I don't see
any point in filling the page cache when it is not needed.
>
> d) The patch could break existing apps.
Since it could break applications that are already (some kind of) broken
that shouldn't be a problem.
So you think it is better to read nothing to the page cache and return
zero instead? This seems like "lying" to the user-space :)
next prev parent reply other threads:[~2005-08-25 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 12:44 [PATCH][RESEND] don't allow sys_readahead() on files opened with O_DIRECT Jan Blunck
2005-08-25 8:24 ` Andrew Morton
2005-08-25 12:13 ` Jan Blunck [this message]
2005-08-25 12:46 ` Christoph Hellwig
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=430DB5E2.9060103@tu-harburg.de \
--to=j.blunck@tu-harburg.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.