mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	mgorman@techsingularity.net, linux-kernel@vger.kernel.org,
	Davidlohr Bueso <dbueso@suse.de>,
	Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] tools/perf-bench: Add basic syscall benchmark
Date: Thu, 14 May 2020 15:39:42 -0500	[thread overview]
Message-ID: <20200514203942.v2dbjeqrdpuucx5h@treble> (raw)
In-Reply-To: <20190308181747.l36zqz2avtivrr3c@linux-r8p5>

On Fri, Mar 08, 2019 at 10:17:47AM -0800, Davidlohr Bueso wrote:
> On Thu, 07 Mar 2019, Arnaldo Carvalho de Melo wrote:
> > You forgot to update tools/perf/Documentation/perf-bench.txt, and please
> > take a look at tools/perf/util/pmu.c convert_scale() to see how to save
> > the current locale, set the one you want, then restore the previous one,
> > so that at the end of this benchmark the environment is back to where it
> > was.
> 
> Here's an updated version with the corresponding docs, but I removed the
> setlocale() - doesn't seem worth it; I hope Mel has no strong objection.
> 
> Thanks.
> 
> -------8<----------------------------------------------------------
> [PATCH v2] tools/perf-bench: Add basic syscall benchmark
> 
> The usefulness of having a standard way of testing syscall performance
> has come up from time to time[0]. Furthermore, some of our testing
> machinery (such as 'mmtests') already makes use of a simplified version
> of the microbenchmark. This patch mainly takes the same idea to measure
> syscall throughput compatible with 'perf-bench' via getppid(2), yet
> without any of the additional template stuff from Ingo's version (based
> on numa.c). The code is identical to what mmtests uses.
> 
> [0] https://lore.kernel.org/lkml/20160201074156.GA27156@gmail.com/
> 
> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>

It would be nice to see this merged.  I posted something very similar
back in 2016.

-- 
Josh


  parent reply	other threads:[~2020-05-14 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 18:52 Davidlohr Bueso
2019-03-07 19:11 ` Arnaldo Carvalho de Melo
2019-03-08 18:17   ` Davidlohr Bueso
2019-03-08 19:48     ` Mel Gorman
2020-05-14 20:39     ` Josh Poimboeuf [this message]
2020-07-26 14:16       ` Arnaldo Carvalho de Melo

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=20200514203942.v2dbjeqrdpuucx5h@treble \
    --to=jpoimboe@redhat.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=dave@stgolabs.net \
    --cc=dbueso@suse.de \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@kernel.org \
    --cc=namhyung@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

all inboxes | Powered by JetHome®