From: Ingo Molnar <mingo@elte.hu>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
suresh.b.siddha@intel.com
Subject: Re: [PATCH] sched: fix a bug in sched domain degenerate
Date: Sat, 8 Nov 2008 09:32:06 +0100 [thread overview]
Message-ID: <20081108083206.GA16667@elte.hu> (raw)
In-Reply-To: <491537C6.3050800@cn.fujitsu.com>
* Li Zefan <lizf@cn.fujitsu.com> wrote:
> Hi Ingo,
>
> I just read the modified changelog in the git-log, and it is
> wrong (or maybe my fix is wrong?), I should have explained
> the bug clearer. :(
>
> I'm writing this mail to confirm if my thought and fix is
> right or not.
>
> > commit f29c9b1ccb52904ee442a933cf3dee628f9f4e62
> > Author: Li Zefan <lizf@cn.fujitsu.com>
> > Date: Thu Nov 6 09:45:16 2008 +0800
> >
> > sched: fix a bug in sched domain degenerate
> >
> > Impact: re-add incorrectly eliminated sched domain layers
> >
>
> This statement is wrong..
that's OK, because the patch is correct :-)
> > (1) on i386 with SCHED_SMT and SCHED_MC enabled
> > # mount -t cgroup -o cpuset xxx /mnt
> > # echo 0 > /mnt/cpuset.sched_load_balance
> > # mkdir /mnt/0
> > # echo 0 > /mnt/0/cpuset.cpus
> > # dmesg
> > CPU0 attaching sched-domain:
> > domain 0: span 0 level CPU
> > groups: 0
> >
>
> I think this behavior is wrong.
>
> > (2) on i386 with SCHED_MC enabled but SCHED_SMT disabled
> > # same with (1)
> > # dmesg
> > CPU0 attaching NULL sched-domain.
> >
>
> And this is right. CPU domain has only 1 cpu so it does not contribute
> to scheduling, so it can be removed.
>
> > The bug is that some sched domains may be skipped unintentionally when
> > degenerating (optimizing) sched domains.
> >
>
> The bug is, some sched domains won't be checked in the for loop due
> to the bug, so they have no chance to be removed.
>
> In the for loop, we check if the parents domains can be removed:
>
> cur_ptr
> |
> v
> SMT--->MC--->CPU--->NULL
>
> (parent MC is checked and can be removed)
>
> =>
>
> cur_ptr
> |
> v
> SMT--->CPU--->NULL
>
> (break out of the for loop, because cur_ptr->parent == NULL)
>
> so CPU domain won't be checked. When we delete MC domain, the pointer
> should not move forwards, so the fix is:
>
> cur_ptr
> |
> v
> SMT--->CPU--->NULL
ah, ok - i misunderstood the direction of the fix. So it strengthens
degeneration - which is a valid fix too. And the commit message
remains there to shame my reading skills forever ;-)
Ingo
prev parent reply other threads:[~2008-11-08 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 1:45 [PATCH] sched: fix a bug in sched domain degenerate Li Zefan
2008-11-06 7:06 ` Ingo Molnar
2008-11-08 6:55 ` Li Zefan
2008-11-08 8:32 ` 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=20081108083206.GA16667@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=suresh.b.siddha@intel.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