From: Kevin Traynor <ktraynor@redhat.com>
To: Joyce Kong <joyce.kong@arm.com>, stable@dpdk.org
Cc: joyce@arm.com
Subject: Re: [dpdk-stable] [PATCH 18.11 1/2] test/rwlock: benchmark on all available cores
Date: Tue, 10 Sep 2019 11:18:32 +0100 [thread overview]
Message-ID: <54c678be-c94e-3e6d-efd3-6322a957d4e6@redhat.com> (raw)
In-Reply-To: <1568086619-5029-1-git-send-email-joyce.kong@arm.com>
On 10/09/2019 04:36, Joyce Kong wrote:
> [ upstream commit fe252fb695efa9deb95f2e6b7baf6f805996a5b0 ]
>
> Add performance test on all available cores to benchmark
> the scaling up performance of rw_lock.
>
> Fixes: af75078fece3 ("first public release")
>
> Suggested-by: Gavin Hu <gavin.hu@arm.com>
> Signed-off-by: Joyce Kong <joyce.kong@arm.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Thanks, added these patches to the queued commits.
prev parent reply other threads:[~2019-09-10 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 3:36 Joyce Kong
2019-09-10 3:36 ` [dpdk-stable] [PATCH 18.11 2/2] test/rwlock: amortize the cost of getting time Joyce Kong
2019-09-10 10:18 ` Kevin Traynor [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=54c678be-c94e-3e6d-efd3-6322a957d4e6@redhat.com \
--to=ktraynor@redhat.com \
--cc=joyce.kong@arm.com \
--cc=joyce@arm.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).