From: Jason Low <jason.low2@hp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Rik van Riel <riel@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Scott Norton <scott.norton@hp.com>,
Aswin Chandramouleeswaran <aswin@hp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jason.low2@hp.com
Subject: Re: [PATCH v2] sched, timer: Use atomics for thread_group_cputimer to improve scalability
Date: Thu, 19 Mar 2015 13:14:14 -0700 [thread overview]
Message-ID: <1426796054.2370.64.camel@j-VirtualBox> (raw)
In-Reply-To: <CA+55aFwyC5YDKgmc_FFi7QEDO_5io+2y-xneMtyuHApsURGaxg@mail.gmail.com>
On Thu, 2015-03-19 at 10:59 -0700, Linus Torvalds wrote:
> On Thu, Mar 19, 2015 at 10:21 AM, Jason Low <jason.low2@hp.com> wrote:
> >
> > I tested this patch on a 32 bit ARM system with 4 cores. Using the
> > generic 64 bit atomics, I did not see any performance change with this
> > patch, and the relevant functions (account_group_*_time(), ect...) don't
> > show up in perf reports.
>
> Ok.
>
> > One factor might be because locking/cacheline contention isn't as
> > apparent on smaller systems to begin with, and lib/atomic64.c also
> > mentions that "this is expected to used on systems with small numbers of
> > CPUs (<= 4 or so)".
>
> Yeah, that's probably a valid argument anyway - 32-bit systems aren't
> really going to be multi-node big systems any more.
>
> So I'm ok with the patch,
Okay, I will be sending out a v3 patch which will also mention a bit
about its effect on 32 bit systems in the changelog, in addition to the
changes that were discussed about in this thread (using WRITE_ONCE(),
ect...).
Thanks,
Jason
next prev parent reply other threads:[~2015-03-19 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 18:42 [PATCH v2] sched, timer: Use atomics for thread_group_cputimer to improve scalability Jason Low
2015-03-02 19:03 ` Linus Torvalds
2015-03-02 21:49 ` Jason Low
2015-03-19 17:21 ` Jason Low
2015-03-19 17:59 ` Linus Torvalds
2015-03-19 20:14 ` Jason Low [this message]
2015-03-02 19:40 ` Oleg Nesterov
2015-03-02 19:43 ` Oleg Nesterov
2015-03-02 21:16 ` Jason Low
2015-03-02 21:44 ` Linus Torvalds
2015-03-02 22:43 ` Jason Low
2015-03-05 15:20 ` Frederic Weisbecker
2015-03-05 20:02 ` Jason Low
2015-03-02 21:19 ` Jason Low
2015-03-05 15:35 ` Frederic Weisbecker
2015-03-05 15:56 ` Paul E. McKenney
2015-03-05 16:00 ` Frederic Weisbecker
2015-03-05 16:16 ` Paul E. McKenney
2015-03-06 0:06 ` Jason Low
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=1426796054.2370.64.camel@j-VirtualBox \
--to=jason.low2@hp.com \
--cc=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=scott.norton@hp.com \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.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