public inbox for [email protected]
 help / color / mirror / Atom feed
From: Dylan Yudaken <[email protected]>
To: "[email protected]" <[email protected]>,
	"[email protected]" <[email protected]>,
	"[email protected]" <[email protected]>
Subject: Re: [PATCH liburing v2 0/3] single-issuer and poll benchmark
Date: Tue, 14 Jun 2022 18:23:55 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Tue, 2022-06-14 at 09:51 -0600, Jens Axboe wrote:
> On 6/14/22 9:48 AM, Pavel Begunkov wrote:
> > On 6/14/22 16:30, Jens Axboe wrote:
> > > On 6/14/22 9:27 AM, Pavel Begunkov wrote:
> > > > Add some tests to check the kernel enforcing single-issuer
> > > > right, and
> > > > add a simple poll benchmark, might be useful if we do poll
> > > > changes.
> > > 
> > > Should we add a benchmark/ or something directory rather than use
> > > examples/ ?
> > > 
> > > I know Dylan was looking at that at one point. I don't feel too
> > > strongly, as long as it doesn't go into test/.
> > 
> > I don't care much myself, I can respin it once (if) the kernel
> > side is queued.
> 
> I'm leaning towards just using examples/ - but maybe Dylan had some
> reasoning for the new directory. CC'ed.
> 

I wanted to have some common framework for benchmarks to make it easy
to write new ones and get some nice numbers. In that case it would make
sense for them to be in one place.

But I haven't finished it yet, so probably for now examples/ is best
and if/when I finish it I can port these over.


  reply	other threads:[~2022-06-14 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 15:27 [PATCH liburing v2 0/3] single-issuer and poll benchmark Pavel Begunkov
2022-06-14 15:27 ` [PATCH liburing v2 1/3] io_uring: update headers with IORING_SETUP_SINGLE_ISSUER Pavel Begunkov
2022-06-14 15:27 ` [PATCH liburing v2 2/3] examples: add a simple single-shot poll benchmark Pavel Begunkov
2022-06-14 15:27 ` [PATCH liburing v2 3/3] tests: test IORING_SETUP_SINGLE_ISSUER Pavel Begunkov
2022-06-14 15:30 ` [PATCH liburing v2 0/3] single-issuer and poll benchmark Jens Axboe
2022-06-14 15:48   ` Pavel Begunkov
2022-06-14 15:51     ` Jens Axboe
2022-06-14 18:23       ` Dylan Yudaken [this message]
2022-06-15  6:24         ` Hao Xu

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=9f85b4b2bddf00b3e2962679a4b3e07f5b6b0e7b.camel@fb.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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