All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yong Zhang <yong.zhang0@gmail.com>
To: Kazuhisa Ichikawa <ki@epsilou.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: Why one of the 2 patches to fix "autogroup" sched problem on UP machines is missing in -rc3?
Date: Tue, 1 Feb 2011 18:46:02 +0800	[thread overview]
Message-ID: <20110201104602.GA3397@zhy> (raw)
In-Reply-To: <AANLkTikYw73nixqMtNSDzus2M5RCN2Zy4PzfbPAxtTBC@mail.gmail.com>

On Tue, Feb 01, 2011 at 06:05:23PM +0900, Kazuhisa Ichikawa wrote:
> Hi Yong,
> 
> Now 2.6.38-rc3 is out, and I think one of the 2 patches you wrote to
> fix "autogroup" sched problem on UP machines is missing there.

Actually the merged one hide the initialising problem.
Because when we enqueue a process to an empty group, update_cfs_shares()
will be called, thus tg->se->load is updated.
enqueue_task_fair()
  update_cfs_shares()
    reweight_entity()
      update_load_set()

> 
> More precisely, your first patch for kernel/sched.c (titled:?sched:
> tg->se->load should be initialised to tg->shares) is missing, while
> the second one for kernel/sched_fair.c (titled:?sched: Fix poor
> interactivity on UP systems due to group scheduler nice tune bug) is
> in -rc3.

See my above answer.

> 
> So what happened to the first patch? Was it superseded and made
> obsolete by the second patch?

Yes.

> 
> # Sorry for not replying to your original post. I'm not subscribing to
> linux kernel mailing list.

Thanks for taking care of this issue :)

Thanks,
Yong

  reply	other threads:[~2011-02-01 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  9:05 Why one of the 2 patches to fix "autogroup" sched problem on UP machines is missing in -rc3? Kazuhisa Ichikawa
2011-02-01 10:46 ` Yong Zhang [this message]
2011-02-01 11:19   ` Kazuhisa Ichikawa

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=20110201104602.GA3397@zhy \
    --to=yong.zhang0@gmail.com \
    --cc=ki@epsilou.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.