From: "M. Fioretti" <m.fioretti@inwind.it>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: "M. Fioretti" <m.fioretti@inwind.it>,
linux-kernel <linux-kernel@vger.kernel.org>,
wli <wli@holomorphy.com>
Subject: Re: Unbloating the kernel, action list
Date: Fri, 17 Oct 2003 22:10:30 +0200 [thread overview]
Message-ID: <20031017201030.GK4943@inwind.it> (raw)
In-Reply-To: <16710000.1066170641@flay>
On Tue, Oct 14, 2003 15:30:41 at 03:30:41PM -0700, Martin J. Bligh (mbligh@aracnet.com) wrote:
>
> > 7) Do come in suggesting anything I might have forgotten
>
> If you do automated testing of nightly builds of the mainline 2.6 / 2.7
> kernels, and point out when they get bigger in consumption, you'll have
> a much better chance of convincing people to fix it when the patch in
> question is still topical, and fresh in people's minds.
I agree. Unfortunately, I have no possibility to do this. I'll pass it
over to the RULE list, though.
> I'd predict that a lot of the issue is just tuning things dynamically
> instead of statically sizing them.
That makes sense. From our point of view, the best thing would be
pointers to resources explaining what to tune, when and why, so we can
prepare suitable documentation from that for our non technical end
users. Suggestions?
TIA,
Marco Fioretti
--
Marco Fioretti m.fioretti, at the server inwind.it
Red Hat for low memory http://www.rule-project.org/en/
I doni ricevuti dal Padreterno, servono se utilizzati: chi li contempla
gode, ma chi ne fa uso probabilmente aiuta altri a godere.
prev parent reply other threads:[~2003-10-17 20:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 11:44 Unbloating the kernel, was: :mem=16MB laptop testing Marco Fioretti
2003-10-14 12:02 ` William Lee Irwin III
2003-10-14 13:24 ` Rik van Riel
2003-10-14 14:30 ` jlnance
2003-10-14 14:54 ` Richard B. Johnson
2003-10-14 16:27 ` Maciej Zenczykowski
2003-10-14 17:33 ` John Bradford
2003-10-14 17:51 ` Richard B. Johnson
2003-10-15 12:43 ` Jan-Benedict Glaw
2003-10-15 13:06 ` William Lee Irwin III
2003-10-15 16:52 ` H. Peter Anvin
2003-10-15 13:08 ` Nick Piggin
2003-10-17 11:50 ` Jan-Benedict Glaw
2003-10-17 23:21 ` Nick Piggin
2003-10-14 18:35 ` tabris
2003-10-14 21:11 ` Roger Larsson
2003-10-15 11:45 ` Jan-Benedict Glaw
2003-10-15 13:06 ` William Lee Irwin III
2003-10-15 13:22 ` Jan-Benedict Glaw
2003-10-24 15:47 ` bill davidsen
2003-10-15 6:06 ` Sandy Harris
2003-10-24 15:59 ` bill davidsen
2003-10-24 16:55 ` M. Fioretti
2003-10-24 17:14 ` bill davidsen
2003-10-25 17:42 ` Geert Uytterhoeven
2003-10-28 9:12 ` Rob Landley
2003-10-14 21:43 ` Unbloating the kernel, action list M. Fioretti
2003-10-14 22:30 ` Martin J. Bligh
2003-10-14 22:56 ` cliff white
2003-10-15 12:48 ` Jan-Benedict Glaw
2003-10-15 13:10 ` William Lee Irwin III
2003-10-15 15:05 ` Jan-Benedict Glaw
2003-10-19 11:21 ` Adrian Bunk
2003-10-21 8:04 ` Jan-Benedict Glaw
2003-10-15 18:16 ` Gabriel Paubert
2003-10-16 5:19 ` Jan-Benedict Glaw
2003-10-16 8:16 ` Gabriel Paubert
2003-10-16 16:16 ` Jan-Benedict Glaw
2003-10-17 20:26 ` M. Fioretti
2003-10-17 20:10 ` M. Fioretti [this message]
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=20031017201030.GK4943@inwind.it \
--to=m.fioretti@inwind.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).