From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: userspace pagecache management tool
Date: Sat, 03 Mar 2007 16:30:56 -0500 [thread overview]
Message-ID: <45E9E910.2070804@redhat.com> (raw)
In-Reply-To: <20070303131204.6706a95c.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Sat, 03 Mar 2007 15:40:42 -0500 Rik van Riel <riel@redhat.com> wrote:
>> I am sick and tired of the "this is hard, let userspace do it" attitude.
>
> Anything you try to do in-kernel will catastrophically screw up some
> workloads. You don't have a chance of getting this right.
Any time you follow the directions of one userspace program,
you can screw up others. I suspect that userspace has far
less of a chance of getting it right than the kernel.
ALSA would be a good example of why it is bad to export
tuning knobs directly to userspace - many sound cards have
non-standard names for the volume controls, making it almost
impossible for userspace to present the user with a simple
user interface for tweaking the volume.
> You are the kernel. The user just read an entire kernel tree. You face a
> binary decision: do you cache that tree or do you not? Your time starts
> now. What is your answer?
Lets turn this around.
The user has been accessing the kernel tree over and over
again, for hours on end (compile testing a patch). Along
comes a backup program, that tells you to evict the whole
thing from the cache.
What do you do?
How can you make global policy decisions based on the intent
of one program?
Only the kernel knows the state of the whole system and has
observed the behaviour of all the processes. One process has
no idea what the other processes in the system are doing.
--
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is. Each group
calls the other unpatriotic.
next prev parent reply other threads:[~2007-03-03 21:31 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 [this message]
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
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=45E9E910.2070804@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox