public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Willy Tarreau <willy@w.ods.org>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Which kernel is the best for a small linux system?
Date: Tue, 14 Mar 2006 09:18:28 +0100	[thread overview]
Message-ID: <1142324308.8075.9.camel@homer> (raw)
In-Reply-To: <20060314072921.GA13969@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Tue, 2006-03-14 at 08:29 +0100, Ingo Molnar wrote:

> and there are some active methods as well: you might want to try Mike 
> Galbraith's scheduler throttling feature:
> 
>  http://lkml.org/lkml/2006/3/3/59
>  http://lkml.org/lkml/2006/3/3/63
> 
> (which we could try in -mm too perhaps, perhaps Mike has an updated 
> patch for 2.6.16-rc6-mm1?)

Yeah, the whole thing is in the attached tarball.  The only significant
difference from last posted version is that setting both tunables to 0
causes 100% of the interactivity stuff to be disabled, returning the
scheduler to pure O(1), but with it's ability to starve mostly neutered.

	-Mike

(delicate tummy warning may be appropriate.. dunno;)

[-- Attachment #2: throttle-V20-2.6.16-rc6-mm1.tar.gz --]
[-- Type: application/x-compressed-tar, Size: 7324 bytes --]

  reply	other threads:[~2006-03-14  8:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  0:40 Which kernel is the best for a small linux system? j4K3xBl4sT3r
2006-03-13  8:00 ` Lexington Luthor
2006-03-15  1:35   ` Grant Coady
2006-03-15  1:46     ` Randy.Dunlap
2006-03-13  8:17 ` Arjan van de Ven
2006-03-13 18:03   ` Grant Coady
2006-03-13 18:06     ` Arjan van de Ven
2006-03-14  6:21       ` Willy Tarreau
2006-03-14  7:29         ` Ingo Molnar
2006-03-14  8:18           ` Mike Galbraith [this message]
2006-03-14  9:05           ` Mike Galbraith
2006-03-14 15:54             ` Willy Tarreau
2006-03-16 15:24             ` Mike Galbraith
2006-03-14 10:03         ` Grant Coady
2006-03-14 22:21           ` Russell King
2006-03-15  0:46             ` Grant Coady
     [not found]               ` <20060315080313.GC3166@flint.arm.linux.org.uk>
2006-03-15  9:37                 ` Grant Coady
2006-03-15 22:53             ` Jan Engelhardt
2006-03-15 23:32               ` Grant Coady
2006-03-16  4:19                 ` Mike Galbraith
2006-03-16  8:12                   ` Mike Galbraith
2006-03-16  8:31                     ` Lee Revell
2006-03-16  8:55                       ` Mike Galbraith
2006-03-16  9:20                         ` Mike Galbraith
2006-03-16  2:55               ` Valdis.Kletnieks
2006-03-13 18:27   ` Sam Ravnborg
2006-03-13 18:41     ` Lee Revell
2006-03-13 19:01       ` Adrian Bunk
2006-03-14  0:18         ` j4K3xBl4sT3r
2006-03-13 19:08     ` Diego Calleja
2006-03-13 22:00     ` Pantelis Antoniou
2006-03-13 22:01       ` j4K3xBl4sT3r
2006-03-13 22:20         ` Pantelis Antoniou
2006-03-13 22:33           ` j4K3xBl4sT3r
2006-03-16 12:03             ` Pavel Machek
2006-03-13 22:25         ` Lee Revell
2006-03-14  3:53           ` Grant Coady
2006-03-15 22:57     ` Jan Engelhardt
2006-03-15 23:10       ` Adrian Bunk
2006-03-16 13:39         ` linux-os (Dick Johnson)

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=1142324308.8075.9.camel@homer \
    --to=efault@gmx.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=willy@w.ods.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