public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: surya.prabhakar@wipro.com, kernel@kolivas.org,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, npiggin@suse.de, efault@gmx.de,
	arjan@infradead.org, tglx@linutronix.de, wli@holomorphy.com,
	Greg KH <gregkh@suse.de>
Subject: Re: [TEST RESULT]massive_intr.c -- cfs/vanilla/sd-0.40
Date: Mon, 16 Apr 2007 12:22:23 +0200	[thread overview]
Message-ID: <20070416102219.GA3950@elte.hu> (raw)
In-Reply-To: <87647wsk2o.wl%takeuchi_satoru@jp.fujitsu.com>


* Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com> wrote:

> You are welcome. I can use larger machine by chance, and also tested 
> there just now.
> 
> Test environment
> ================
> 
>  - kernel:         2.6.21-rc6-CFS
>  - run time:       300 secs
>  - # of CPU:       12
>  - # of processes: 200 or 2400
> 
> Result
> ===================================
> 
>   +----------+-----------+-------+------+------+--------+
>   |   # of   |   # of    | avg   | max  | min  |  stdev |
>   |   CPUs   | processes |       |      |      |        |
>   +----------+-----------+-------+------+------+--------+
>   |          |       200 |  2250 | 2348 | 2204 |     64 |
>   | 12(ia64) +-----------+-------+------+------+--------+
>   |          |      2400 | 187.5 |  197 |  176 |    4.3 |
>   +----------+-----------+-------+------+------+--------+
> 
> Looks like good too.

yeah. The spread between min and max is 11%, the spread between stddev 
and avg is 2.2%, which is quite OK for so many tasks.

> BTW, I've a question. Actually this problem is fixed on CFS and DS. 
> However they are mostly written from scratch and doeesn't suitable for 
> stable version, for example 2.6.20.X. Can your other patch be 
> compromise for stable version? Although that patch is not perfect, but 
> I think it's preferable to leave it alone.

i'm afraid that small patch is not suitable for a general purpose Linux 
release (it hits interactivity way too much) - that's what this 
years-long struggle was about. But you could apply it to a special 
server-centric kernel.

	Ingo

      reply	other threads:[~2007-04-16 10:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-14  8:49 [TEST RESULT]massive_intr.c -- cfs/vanilla/sd-0.40 surya.prabhakar
2007-04-14  9:06 ` Willy Tarreau
2007-04-14 12:02 ` Ingo Molnar
2007-04-14 19:55   ` William Lee Irwin III
2007-04-16  8:26   ` Satoru Takeuchi
2007-04-16  8:47     ` Ingo Molnar
2007-04-16 10:13       ` Satoru Takeuchi
2007-04-16 10:22         ` Ingo Molnar [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=20070416102219.GA3950@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=efault@gmx.de \
    --cc=gregkh@suse.de \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=surya.prabhakar@wipro.com \
    --cc=takeuchi_satoru@jp.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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