From: "R. J. Wysocki" <rjwysocki@sisk.pl>
To: Nick Piggin <nickpiggin@yahoo.com.au>, Con Kolivas <kernel@kolivas.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Autotune swappiness01
Date: Mon, 26 Jul 2004 15:53:09 +0200 [thread overview]
Message-ID: <200407261553.09594.rjwysocki@sisk.pl> (raw)
In-Reply-To: <4104EF5F.9070405@yahoo.com.au>
On Monday 26 of July 2004 13:47, Nick Piggin wrote:
> Con Kolivas wrote:
> > Nick Piggin wrote:
> >> Con Kolivas wrote:
> >>> In my ideal, nonsensical, impossible to obtain world we have an
> >>> autoregulating operating system that doesn't need any knobs.
> >>
> >> Some thinks are fundamental tradeoffs that can't be autotuned.
> >>
> >> Latency vs throughput comes up in a lot of places, eg. timeslices.
> >>
> >> Maximum throughput via effective use of swap, versus swapping as
> >> a last resort may be another.
> >
> > As I said... it was ideal, nonsensical, and impossible. Doesn't sound
> > like you're arguing with me.
>
> No, you're right. My ideal operating system knows what the user
> wants too ;)
Well, what I hate about various computer programs is that they seem to assume
to know what I (the USER) want and they don't let me do anything else that
they "know" what I should/would do. ;-)
> Most of the time though, you are right. The quality/desirability of an
> implementation will be inversely proportional to the number of knobs
> sticking out of it (with bonus points for those that are meaningful to
> 2 people on the planet).
Can you please tell me why you think that the least tunable implementation
should be the best/most desirable one? I always prefer the most tunable
implementations which is quite opposite to what you have said, but this is my
personal opinion, of course.
Yours,
rjw
--
Rafael J. Wysocki
[tel. (+48) 605 053 693]
----------------------------
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
-- Richard P. Feynman
next prev parent reply other threads:[~2004-07-26 13:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 0:25 [PATCH][2.6.8-rc1-mm1] " Con Kolivas
2004-07-26 0:36 ` Andrew Morton
2004-07-26 0:43 ` Con Kolivas
2004-07-26 0:48 ` Andrew Morton
2004-07-26 1:01 ` Con Kolivas
2004-07-26 1:09 ` Con Kolivas
2004-07-26 8:52 ` R. J. Wysocki
2004-07-26 9:31 ` Con Kolivas
2004-07-26 10:34 ` R. J. Wysocki
2004-07-26 10:29 ` Con Kolivas
2004-07-26 10:54 ` R. J. Wysocki
2004-07-26 11:03 ` Con Kolivas
2004-07-26 11:13 ` Nick Piggin
2004-07-26 11:17 ` Con Kolivas
2004-07-26 11:47 ` Nick Piggin
2004-07-26 13:53 ` R. J. Wysocki [this message]
2004-07-26 18:45 ` Adam Kropelin
2004-07-26 18:53 ` R. J. Wysocki
2004-07-26 17:55 ` Gerrit Huizenga
2004-07-26 20:29 ` Joel Becker
2004-07-26 20:42 ` Andrew Morton
2004-07-26 22:58 ` Con Kolivas
2004-07-27 0:52 ` Clemens Schwaighofer
2004-07-27 1:09 ` Andrew Morton
2004-07-27 1:17 ` Clemens Schwaighofer
2004-07-27 2:03 ` Tim Connors
2004-07-27 2:43 ` Con Kolivas
2004-07-27 3:02 ` Tim Connors
2004-07-27 3:43 ` Clemens Schwaighofer
2004-07-27 3:47 ` Joel Becker
2004-07-27 15:32 ` William Lee Irwin III
2004-07-27 3:41 ` Clemens Schwaighofer
2004-07-26 14:52 Martin Knoblauch
2004-07-26 21:29 DaMouse
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=200407261553.09594.rjwysocki@sisk.pl \
--to=rjwysocki@sisk.pl \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®