From: Clemens Schwaighofer <cs@tequila.co.jp>
To: Tim Connors <tconnors+linuxkml@astro.swin.edu.au>
Cc: Con Kolivas <kernel@kolivas.org>, Andrew Morton <akpm@osdl.org>,
Joel.Becker@oracle.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Autotune swappiness01
Date: Tue, 27 Jul 2004 12:43:38 +0900 [thread overview]
Message-ID: <4105CF6A.8070504@tequila.co.jp> (raw)
In-Reply-To: <Pine.LNX.4.53.0407271250210.23847@tellurium.ssi.swin.edu.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tim Connors wrote:
| On Tue, 27 Jul 2004, Con Kolivas wrote:
| Then there's the relative importance of subjective "feel", vs hard
| numbers. Maybe some people prefer that their system feels nicer, even if
| it doesn't compile kernels so fast. And I think this decision is best left
| to at least one of those knobs (hey, all you know, people might even
| adjust the knob in a crontab).
I think, the more linux users are out there, the less is the percentage
who compiles kernels often. And often means once or twice a day. Most
people use stock kernels. I think a "knob" that says "compile a lot" or
"normal" or "server" or so would be nice.
Especially because a server has very different need of swap, etc than a
workstation.
- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
TEQUILA\Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.co.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBBc9qjBz/yQjBxz8RAqrJAKDkBo7ZnYzWOqdXABRUPYUoO1ooSACffSnk
uTERz/dQaEV1lSUsCEdsRhk=
=EBxd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-27 3: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] Autotune swappiness01 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
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 [this message]
2004-07-27 3:47 ` Joel Becker
2004-07-27 15:32 ` William Lee Irwin III
2004-07-27 3:41 ` Clemens Schwaighofer
-- strict thread matches above, loose matches on Subject: below --
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=4105CF6A.8070504@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=Joel.Becker@oracle.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tconnors+linuxkml@astro.swin.edu.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