From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jie Chen <chen@jlab.org>
Cc: linux-kernel@vger.kernel.org, Eric Dumazet <dada1@cosmosbay.com>,
Ingo Molnar <mingo@elte.hu>,
Simon Holm Th??gersen <odie@cs.aau.dk>
Subject: Re: Possible bug from kernel 2.6.22 and above
Date: Wed, 05 Dec 2007 21:36:42 +0100 [thread overview]
Message-ID: <1196887002.6353.19.camel@lappy> (raw)
In-Reply-To: <4744966C.900@jlab.org>
On Wed, 2007-11-21 at 15:34 -0500, Jie Chen wrote:
> It is clearly that the synchronization overhead increases as the number
> of threads increases in the kernel 2.6.21. But the synchronization
> overhead actually decreases as the number of threads increases in the
> kernel 2.6.23.8 (We observed the same behavior on kernel 2.6.22 as
> well). This certainly is not a correct behavior. The kernels are
> configured with CONFIG_SMP, CONFIG_NUMA, CONFIG_SCHED_MC,
> CONFIG_PREEMPT_NONE, CONFIG_DISCONTIGMEM set. The complete kernel
> configuration file is in the attachment of this e-mail.
>
> From what we have read, there was a new scheduler (CFS) appeared from
> 2.6.22. We are not sure whether the above behavior is caused by the new
> scheduler.
If I read this correctly, you say that: .22 is the first bad one right?
The new scheduler (CFS) was introduced in .23, so it seems another
change would be responsible for this.
next prev parent reply other threads:[~2007-12-05 21:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 20:34 Possible bug from kernel 2.6.22 and above Jie Chen
2007-11-21 22:14 ` Eric Dumazet
2007-11-22 1:52 ` Jie Chen
2007-11-22 2:32 ` Simon Holm Thøgersen
2007-11-22 2:58 ` Jie Chen
2007-11-22 20:19 ` Matt Mackall
2007-12-04 13:17 ` Possible bug from kernel 2.6.22 and above, 2.6.24-rc4 Ingo Molnar
2007-12-04 15:41 ` Jie Chen
2007-12-05 15:29 ` Jie Chen
2007-12-05 15:40 ` Ingo Molnar
2007-12-05 16:16 ` Eric Dumazet
2007-12-05 16:25 ` Ingo Molnar
2007-12-05 16:29 ` Eric Dumazet
2007-12-05 16:22 ` Jie Chen
2007-12-05 16:47 ` Ingo Molnar
2007-12-05 17:47 ` Jie Chen
2007-12-05 20:03 ` Ingo Molnar
2007-12-05 20:23 ` Jie Chen
2007-12-05 20:46 ` Ingo Molnar
2007-12-05 20:52 ` Jie Chen
2007-12-05 21:02 ` Ingo Molnar
2007-12-05 22:16 ` Jie Chen
2007-12-06 10:43 ` Ingo Molnar
2007-12-06 16:29 ` Jie Chen
2007-12-10 10:59 ` Ingo Molnar
2007-12-10 20:04 ` Jie Chen
2007-12-11 10:51 ` Ingo Molnar
2007-12-11 15:28 ` Jie Chen
2007-12-11 15:52 ` Ingo Molnar
2007-12-11 16:39 ` Jie Chen
2007-12-11 21:23 ` Ingo Molnar
2007-12-11 22:11 ` Jie Chen
2007-12-12 12:49 ` Peter Zijlstra
2007-12-05 20:36 ` Peter Zijlstra [this message]
2007-12-05 20:53 ` Possible bug from kernel 2.6.22 and above Jie Chen
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=1196887002.6353.19.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=chen@jlab.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=odie@cs.aau.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.