From: Wei Yang <weiyang@linux.vnet.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: Wei Yang <weiyang@linux.vnet.ibm.com>,
cl@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] percpu: stop the loop when a cpu belongs to a new group
Date: Mon, 28 Oct 2013 11:00:55 +0800 [thread overview]
Message-ID: <20131028030055.GC15642@weiyang.vnet.ibm.com> (raw)
In-Reply-To: <20131027123008.GJ14934@mtj.dyndns.org>
On Sun, Oct 27, 2013 at 08:30:08AM -0400, Tejun Heo wrote:
>On Mon, Oct 21, 2013 at 04:58:11PM +0800, Wei Yang wrote:
>> When a cpu belongs to a new group, there is no cpu has the same group id. This
>> means it can be assigned a new group id without checking with every others.
>>
>> This patch does this optimiztion.
>
>Does this actually matter? If so, it'd probably make a lot more sense
>to start inner loop at @cpu + 1 so that it becomes O(N).
One of the worst case in my mind:
CPU: 0 1 2 3 4 ...
Group: 0 1 2 3 4 ...
(sounds it is impossible in the real world)
Every time, when we encounter a new CPU and try to assign it to a group, we
found it belongs to a new group. The original logic will iterate on all old
CPUs again, while the new logic could skip this and assign it to a new group.
Again, this is a tiny change, which doesn't matters a lot.
BTW, I don't get your point for "start inner loop at @cpu+1".
The original logic is:
loop 1: 0 - nr_cpus
loop 2: 0 - (cpu - 1)
If you found one better approach to improve the logic, I believe all the users
will appreciate your efforts :-)
Thanks for your review and comments again ~
>
>Thanks.
>
>--
>tejun
--
Richard Yang
Help you, Help me
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-10-28 3:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 8:58 [PATCH 1/3] percpu: stop the loop when a cpu belongs to a new group Wei Yang
2013-10-21 8:58 ` [PATCH 2/3] percpu: merge two loops when setting up group info Wei Yang
2013-10-27 12:35 ` Tejun Heo
2013-10-28 2:37 ` Wei Yang
2013-10-21 8:58 ` [PATCH 3/3] percpu: little optimization on calculating pcpu_unit_size Wei Yang
2013-10-27 12:36 ` Tejun Heo
2013-10-28 2:43 ` Wei Yang
2013-10-27 12:30 ` [PATCH 1/3] percpu: stop the loop when a cpu belongs to a new group Tejun Heo
2013-10-28 3:00 ` Wei Yang [this message]
2013-10-28 11:31 ` Tejun Heo
2013-10-28 15:17 ` Wei Yang
2013-11-20 3:00 ` Wei Yang
2013-11-20 5:51 ` Tejun Heo
2013-11-20 6:58 ` Wei Yang
2013-11-22 23:04 ` Tejun Heo
2013-11-24 1:48 ` Wei Yang
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=20131028030055.GC15642@weiyang.vnet.ibm.com \
--to=weiyang@linux.vnet.ibm.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.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).