linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Nick Piggin <npiggin@suse.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Miklos Szeredi <miklos@szeredi.hu>,
	peterz@infradead.org, fweisbec@gmail.com, tardyp@gmail.com,
	mingo@elte.hu, acme@redhat.com, tzanussi@gmail.com,
	paulus@samba.org, linux-kernel@vger.kernel.org,
	arjan@infradead.org, ziga.mahkovec@gmail.com,
	davem@davemloft.net, linux-mm@kvack.org,
	akpm@linux-foundation.org, kosaki.motohiro@jp.fujitsu.com,
	cl@linux-foundation.org, tj@kernel.org, jens.axboe@oracle.com,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: Unexpected splice "always copy" behavior observed
Date: Thu, 20 May 2010 07:18:21 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1005200715460.23538@i5.linux-foundation.org> (raw)
In-Reply-To: <20100520015605.GA28411@Krystal>



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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-05-20 14:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 15:34 Mathieu Desnoyers
2010-05-18 15:51 ` Nick Piggin
2010-05-18 15:56   ` Christoph Lameter
2010-05-18 16:00     ` Nick Piggin
2010-05-18 16:13       ` Nick Piggin
2010-05-18 15:53 ` Steven Rostedt
2010-05-18 16:10   ` Steven Rostedt
2010-05-18 16:25     ` Linus Torvalds
2010-05-19  6:31       ` Nick Piggin
2010-05-19 14:39         ` Linus Torvalds
2010-05-19 14:56           ` Steven Rostedt
2010-05-19 14:59             ` Linus Torvalds
2010-05-19 15:12               ` Steven Rostedt
2010-05-19 15:51                 ` Mathieu Desnoyers
2010-05-19 15:33               ` Miklos Szeredi
2010-05-19 15:45                 ` Steven Rostedt
2010-05-19 15:55                   ` Nick Piggin
2010-05-19 16:01                     ` Mathieu Desnoyers
2010-05-19 16:36                     ` Steven Rostedt
2010-05-19 15:57                   ` Mathieu Desnoyers
2010-05-19 16:27                     ` Nick Piggin
2010-05-19 19:14                       ` Mathieu Desnoyers
2010-05-19 19:31                         ` Linus Torvalds
2010-05-19 21:49                           ` Mathieu Desnoyers
2010-05-20  0:04                             ` Linus Torvalds
2010-05-20  1:56                               ` Mathieu Desnoyers
2010-05-20 14:18                                 ` Linus Torvalds [this message]
2010-05-19 20:59               ` Rick Sherm
2010-05-19 15:17           ` Nick Piggin
2010-05-19 15:30             ` Linus Torvalds
2010-05-19 15:44               ` Nick Piggin
2010-05-19 15:28           ` Miklos Szeredi
2010-05-19 15:32             ` Linus Torvalds
2010-05-19 15:56               ` Miklos Szeredi
2010-05-19 16:01                 ` Linus Torvalds

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=alpine.LFD.2.00.1005200715460.23538@i5.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=cl@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=fweisbec@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=miklos@szeredi.hu \
    --cc=mingo@elte.hu \
    --cc=mtk.manpages@gmail.com \
    --cc=npiggin@suse.de \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tardyp@gmail.com \
    --cc=tj@kernel.org \
    --cc=tzanussi@gmail.com \
    --cc=ziga.mahkovec@gmail.com \
    /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