From: Thomas Monjalon <thomas@monjalon.net>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: honnappa.nagarahalli@arm.com, andrew.rybchenko@oktetlabs.ru,
dev@dpdk.org, fengchengwen@huawei.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v7] mempool: test performance with larger bursts
Date: Mon, 16 Sep 2024 16:04:11 +0200 [thread overview]
Message-ID: <3640825.iIbC2pHGDl@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F6EC@smartserver.smartshare.dk>
16/09/2024 15:08, Morten Brørup:
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Monday, 16 September 2024 14.41
> >
> > 13/09/2024 16:58, Morten Brørup:
> > > PING for apply.
> > >
> > > Patch has 2 acks.
> > > And since it was signed off by a co-maintainer (myself),
> > > I don't think an ack from the other co-maintainer (Andrew) is required.
> > > Please correct me if I'm wrong?
> >
> >
> > It's not a matter of acks.
> >
> > I feel we should reduce from 5 seconds to 1 second as part of this patch.
>
> As mentioned below, I was worried about reducing the test duration.
> If you think the test will be accurate enough, I can easily reduce it to 1; you're not the only person annoyed by the long test duration.
I cannot be sure but it's probably worth to try.
> > But seeing there is no more comments, I suppose I should apply this version.
>
> Should I send v8 with reduced test duration from 5 to 1 second?
If you agree to try this duration, yes please send a v8.
next prev parent reply other threads:[~2024-09-16 14:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 4:52 [PATCH] mempool: test performance with larger bursts Morten Brørup
2024-01-22 7:10 ` fengchengwen
2024-01-22 14:34 ` [PATCH v2] " Morten Brørup
2024-01-24 2:41 ` fengchengwen
2024-01-24 8:58 ` [PATCH v3] " Morten Brørup
2024-01-24 9:10 ` [PATCH v4] " Morten Brørup
2024-01-24 11:21 ` [PATCH v5] " Morten Brørup
2024-02-18 18:03 ` Thomas Monjalon
2024-02-20 13:49 ` Morten Brørup
2024-02-21 10:22 ` Thomas Monjalon
2024-02-21 10:38 ` Morten Brørup
2024-02-21 10:40 ` Bruce Richardson
2024-02-20 14:01 ` [PATCH v6] " Morten Brørup
2024-03-02 20:04 ` [PATCH v7] " Morten Brørup
2024-04-04 9:26 ` Morten Brørup
2024-06-10 8:56 ` Morten Brørup
2024-06-18 13:21 ` Bruce Richardson
2024-06-18 13:48 ` Morten Brørup
2024-09-13 14:58 ` Morten Brørup
2024-09-16 12:40 ` Thomas Monjalon
2024-09-16 13:08 ` Morten Brørup
2024-09-16 14:04 ` Thomas Monjalon [this message]
2024-09-16 15:37 ` [PATCH v8] " Morten Brørup
2024-09-17 8:10 ` [PATCH v9] " Morten Brørup
2024-10-08 9:14 ` Morten Brørup
2024-10-11 12:50 ` David Marchand
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=3640825.iIbC2pHGDl@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=mb@smartsharesystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.