From: Andrew Morton <akpm@linux-foundation.org>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: userspace pagecache management tool
Date: Sat, 3 Mar 2007 14:37:14 -0800 [thread overview]
Message-ID: <20070303143714.cdd83690.akpm@linux-foundation.org> (raw)
In-Reply-To: <45E9F5DA.2070708@redhat.com>
On Sat, 03 Mar 2007 17:25:30 -0500 Rik van Riel <riel@redhat.com> wrote:
> Andrew Morton wrote:
>
> > Well, backup programs are a unique case. Let's say instead that the user
> > has just generated a 600MB ISO image.
> >
> > The kernel *just doesn't know* whether the user will next try to read the
> > kernel tree or will next try to read that ISO image.
> >
> > That, Rik, is my point, and is the entire point of this work.
>
> I still don't understand why "the backup program flushed my data out
> of the cache with POSIX_FADV_DONTNEED" is an improvement over "the
> backup program flushed my data out of the cache by reading other files".
Oh. Well, yes, if the user elected to instruct the backup program to
invalidate both its input files and its output files and if it's a full
dump, you end up with nothing in pagecache. Possibly a more sensible
setting would be to invalidate only the output.
But having some batch program come in from the side and perform a bulk read
of your present working set isn't very common.
> Your code may be useful for a few specialized situations,
That's quite wrong. It is useful for a great number of well-known problem
scenarios, all of which are *already "specialized situations". It's *you*
who is chasing down the 1% scenarios and portraying them as general problems.
Backups only happen once in 24 hours, for example.
> but I don't
> see it actually fixing most of the examples you gave in your
> announcement, except for the DVD copying one.
>
I don't know how much benefit it will provide for the updatedb problem - I
expect it'll help sometimes. otoh maybe it'll worsen the existing slab internal
fragmentation problem, dunno.
But the other scenarios it solves completely and optimally.
next prev parent reply other threads:[~2007-03-03 22:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 20:29 userspace pagecache management tool Andrew Morton
2007-03-03 20:40 ` Rik van Riel
2007-03-03 21:12 ` Andrew Morton
2007-03-03 21:30 ` Rik van Riel
2007-03-03 21:41 ` bert hubert
2007-03-03 22:14 ` Andrew Morton
2007-03-03 22:19 ` Rik van Riel
2007-03-03 22:26 ` Andrew Morton
2007-03-03 22:28 ` Rik van Riel
2007-03-03 22:38 ` Andrew Morton
2007-03-03 22:56 ` Erik Andersen
2007-03-03 23:01 ` bert hubert
2007-03-03 23:45 ` Andrew Morton
2007-03-06 12:10 ` Pádraig Brady
2007-03-06 21:40 ` Andrew Morton
2007-03-06 21:44 ` Rik van Riel
2007-03-07 11:39 ` Pádraig Brady
2007-03-07 18:50 ` Andrew Morton
2007-03-08 7:59 ` Vaidyanathan Srinivasan
2007-03-08 8:12 ` Andrew Morton
2007-03-03 22:07 ` Andrew Morton
2007-03-03 22:25 ` Rik van Riel
2007-03-03 22:37 ` Andrew Morton [this message]
2007-03-03 22:52 ` Andrew Morton
2007-03-04 0:01 ` Rik van Riel
2007-03-04 1:02 ` Andrew Morton
2007-03-04 1:23 ` Rik van Riel
2007-03-04 1:49 ` Andrew Morton
2007-03-04 1:56 ` Rik van Riel
2007-03-04 12:07 ` Andrew Morton
2007-03-04 14:35 ` Peter Zijlstra
2007-03-04 16:01 ` Rik van Riel
2007-03-03 22:58 ` Ray Lee
2007-03-03 23:34 ` Andrew Morton
2007-03-04 1:02 ` Ray Lee
2007-03-04 1:21 ` Andrew Morton
2007-03-04 0:14 ` Eric St-Laurent
2007-03-04 1:10 ` Andrew Morton
2007-03-04 1:39 ` Rik van Riel
2007-03-04 1:16 ` Lee Revell
2007-03-04 1:39 ` Andrew Morton
2007-03-04 2:35 ` Lee Revell
2007-03-04 4:35 ` Andrew Morton
2007-03-05 11:02 ` Pádraig Brady
2007-03-05 11:12 ` Andrew Morton
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=20070303143714.cdd83690.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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