public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hideaki Kimura <hideaki.kimura@hpe.com>
To: Jason Low <jason.low@hpe.com>, Ingo Molnar <mingo@kernel.org>
Cc: Jason Low <jason.low2@hp.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	George Spelvin <linux@horizon.com>,
	terry.rudd@hpe.com, scott.norton@hpe.com
Subject: Re: [PATCH v2 0/4] timer: Improve itimers scalability
Date: Fri, 16 Oct 2015 10:46:30 -0700	[thread overview]
Message-ID: <562137F6.6080905@hpe.com> (raw)
In-Reply-To: <1445016853.2517.16.camel@j-VirtualBox>

Removing dependency to the database code is trivial. It's just 100 lines 
that launch lots of threads and do NUMA-aware memory accesses so that 
remote NUMA access cost does not affect the benchmark.

It's just a bit tedious to convert the C++11 code into C/pthread.
C++11 really spoiled me.
Still, not much work. Let me know where to post the code.

On 10/16/2015 10:34 AM, Jason Low wrote:
>> Mind posting it, so that people can stick it into a new 'perf bench timer'
>> subcommand, and/or reproduce your results with it?
>
> Yes, sure. At the moment, this micro benchmark is written in C++ and
> integrated with the database code. We can look into rewriting it into a
> more general program so that it can be included in perf.
>
> Thanks,
> Jason
>

-- 
Hideaki Kimura

      reply	other threads:[~2015-10-16 18:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 19:07 [PATCH v2 0/4] timer: Improve itimers scalability Jason Low
2015-10-14 19:07 ` [PATCH v2 1/4] timer: Optimize fastpath_timer_check() Jason Low
2015-10-15  9:27   ` [tip:timers/core] posix_cpu_timer: Optimize fastpath_timer_check( ) tip-bot for Jason Low
2015-10-14 19:07 ` [PATCH v2 2/4] timer: Check thread timers only when there are active thread timers Jason Low
2015-10-15  9:28   ` [tip:timers/core] posix_cpu_timer: " tip-bot for Jason Low
2015-10-14 19:07 ` [PATCH v2 3/4] timer: Convert cputimer->running to bool Jason Low
2015-10-15  9:28   ` [tip:timers/core] posix_cpu_timer: Convert cputimer-> running " tip-bot for Jason Low
2015-10-14 19:07 ` [PATCH v2 4/4] timer: Reduce unnecessary sighand lock contention Jason Low
2015-10-15  9:28   ` [tip:timers/core] posix_cpu_timer: " tip-bot for Jason Low
2015-10-14 21:18 ` [PATCH v2 0/4] timer: Improve itimers scalability George Spelvin
2015-10-15 12:30   ` Frederic Weisbecker
2015-10-15 19:00   ` Jason Low
2015-10-15  8:47 ` Ingo Molnar
2015-10-15 19:01   ` Jason Low
2015-10-16  7:12     ` Ingo Molnar
2015-10-16 17:34       ` Jason Low
2015-10-16 17:46         ` Hideaki Kimura [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=562137F6.6080905@hpe.com \
    --to=hideaki.kimura@hpe.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@stgolabs.net \
    --cc=fweisbec@gmail.com \
    --cc=jason.low2@hp.com \
    --cc=jason.low@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=scott.norton@hpe.com \
    --cc=terry.rudd@hpe.com \
    --cc=tglx@linutronix.de \
    /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