[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1005200715460.23538@i5.linux-foundation.org>
Date: Thu, 20 May 2010 07:18:21 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
cc: Nick Piggin <npiggin@...e.de>,
Steven Rostedt <rostedt@...dmis.org>,
Miklos Szeredi <miklos@...redi.hu>, peterz@...radead.org,
fweisbec@...il.com, tardyp@...il.com, mingo@...e.hu,
acme@...hat.com, tzanussi@...il.com, paulus@...ba.org,
linux-kernel@...r.kernel.org, arjan@...radead.org,
ziga.mahkovec@...il.com, davem@...emloft.net, linux-mm@...ck.org,
akpm@...ux-foundation.org, kosaki.motohiro@...fujitsu.com,
cl@...ux-foundation.org, tj@...nel.org, jens.axboe@...cle.com,
Michael Kerrisk <mtk.manpages@...il.com>,
linux-man@...r.kernel.org
Subject: Re: Unexpected splice "always copy" behavior observed
On Wed, 19 May 2010, Mathieu Desnoyers wrote:
>
> Programs can use posix_fadvise() to announce an intention to access
> file data in a specific pattern in the future, thus allowing the kernel
> to perform appropriate optimizations.
It's true for some of them. The random-vs-linear behavior is a flag for
the future, for example (relevant for prefetching).
In fact, it's technically true even for DONTNEED. It's true that we won't
need the pages in the future! So we throw the pages away. But that means
that we throw the _current_ pages away.
If we actually touch pages later, than that obviously invalidates the fact
that we said 'DONTNEED' - we clearly needed them.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists