From: David Greaves <david@dgreaves.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: POSIX_FADV_NOREUSE and O_STREAMING behavior in 2.6.7
Date: Fri, 27 Aug 2004 09:25:21 +0100 [thread overview]
Message-ID: <412EEFF1.9080409@dgreaves.com> (raw)
In-Reply-To: <1093547459.6106.57.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>På to , 26/08/2004 klokka 14:38, skreiv David Greaves:
>
>
>>David Rolenc wrote:
>>
>>
>>
>>>I am trying to get O_STREAMING (Robert Love patch for 2.4) behavior in
>>>2.6 and just a glance at fadvise.c suggests that POSIX_FADV_NOREUSE is
>>>not implemented any differently than POSIX_FADV_WILLNEED. Am I missing
>>>something? I want to read data from disk with readahead and drop the
>>>data from the page cache as soon as I am done with it. Do I have to
>>>call fadvise with POSIX_FADV_DONTNEED after every read?
>>>
>>>
>>And will this work over nfs?
>>
>>
>
>What do you mean?
>
>The client will of course respect fadvise() if the generic VM code
>supports it, but there is no NFS protocol support for this, so the
>client is not able to communicate your fadvise call on to the server.
>
>
Perfect answer
thank you
I want my nfs client to communicate this to my nfs server. Thus avoiding
my nfs server having a cache of useless video.
I can see this becoming an important benefit for video distribution (an
area linux is likely to see more of)
David
next prev parent reply other threads:[~2004-08-27 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 17:39 POSIX_FADV_NOREUSE and O_STREAMING behavior in 2.6.7 David Rolenc
2004-08-26 18:17 ` Robert Love
2004-08-26 19:23 ` David Rolenc
2004-08-26 18:38 ` David Greaves
2004-08-26 19:11 ` Trond Myklebust
2004-08-27 8:25 ` David Greaves [this message]
2004-08-27 17:21 ` Trond Myklebust
2004-08-27 17:37 ` Trond Myklebust
2004-08-26 19:11 ` David Rolenc
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=412EEFF1.9080409@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.