From: Rakib Mullick <rakib.mullick@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Add rq->nr_uninterruptible count to dest cpu's rq while CPU goes down.
Date: Wed, 29 Aug 2012 07:05:07 +0600 [thread overview]
Message-ID: <CADZ9YHj9KmWU+A9MnNPDEPsEjzb2_ArCLFvt6d+fsGgXmpLfaQ@mail.gmail.com> (raw)
In-Reply-To: <20120828170734.GT2961@linux.vnet.ibm.com>
On 8/28/12, Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
>
> OK, but I thought that Peter said that ->nr_uninterruptible was
> meaningful only when summed across all CPUs. If that is the case,
> it shouldn't matter where the counts are moved.
>
Yes, right. But, nr_uninterruptible is also use to calculate delta.
Please see calc_load_fold_active().
Thanks,
Rakib.
next prev parent reply other threads:[~2012-08-29 1:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 13:45 Add rq->nr_uninterruptible count to dest cpu's rq while CPU goes down Rakib Mullick
2012-08-16 13:56 ` Peter Zijlstra
2012-08-16 14:28 ` Rakib Mullick
2012-08-16 14:42 ` Peter Zijlstra
2012-08-16 15:32 ` Rakib Mullick
2012-08-16 17:46 ` Peter Zijlstra
2012-08-17 13:39 ` Rakib Mullick
2012-08-20 9:26 ` Peter Zijlstra
2012-08-20 16:10 ` Rakib Mullick
2012-08-20 16:16 ` Peter Zijlstra
2012-08-20 16:26 ` Paul E. McKenney
2012-08-27 18:44 ` Paul E. McKenney
2012-08-28 6:57 ` Rakib Mullick
2012-08-28 13:42 ` Paul E. McKenney
2012-08-28 16:52 ` Rakib Mullick
2012-08-28 17:07 ` Paul E. McKenney
2012-08-29 1:05 ` Rakib Mullick [this message]
2012-09-04 18:43 ` [tip:sched/core] sched: Fix load avg vs cpu-hotplug tip-bot for Peter Zijlstra
2012-09-05 12:36 ` Peter Zijlstra
2012-09-05 13:29 ` Ingo Molnar
2012-09-05 17:01 ` Peter Zijlstra
2012-09-05 17:34 ` Ingo Molnar
2012-09-05 22:03 ` Peter Zijlstra
2012-09-05 23:39 ` Paul E. McKenney
2012-09-06 3:30 ` Rakib Mullick
2012-09-14 6:14 ` [tip:sched/core] sched: Fix load avg vs. cpu-hotplug tip-bot for Peter Zijlstra
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=CADZ9YHj9KmWU+A9MnNPDEPsEjzb2_ArCLFvt6d+fsGgXmpLfaQ@mail.gmail.com \
--to=rakib.mullick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).