From: "Wang, Yipeng1" <yipeng1.wang@intel.com>
To: Stanislaw Kardach <kda@semihalf.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Frank Zhao <Frank.Zhao@starfivetech.com>,
Sam Grove <sam.grove@sifive.com>,
"mw@semihalf.com" <mw@semihalf.com>,
"upstream@semihalf.com" <upstream@semihalf.com>
Subject: RE: [PATCH 1/1] test/hash: report non HTM numbers for single r/w
Date: Tue, 10 May 2022 22:09:55 +0000 [thread overview]
Message-ID: <CO1PR11MB51723FFC4433972B58D145FAC3C99@CO1PR11MB5172.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220510115734.457718-1-kda@semihalf.com>
> -----Original Message-----
> From: Stanislaw Kardach <kda@semihalf.com>
> Sent: Tuesday, May 10, 2022 4:58 AM
> To: Wang, Yipeng1 <yipeng1.wang@intel.com>
> Cc: Stanislaw Kardach <kda@semihalf.com>; dev@dpdk.org; Frank Zhao
> <Frank.Zhao@starfivetech.com>; Sam Grove <sam.grove@sifive.com>;
> mw@semihalf.com; upstream@semihalf.com
> Subject: [PATCH 1/1] test/hash: report non HTM numbers for single r/w
>
> In hash_readwrite_perf_autotest a single read and write operation is
> benchmarked for both HTM and non HTM cases. However the result
> summary only shows the HTM value. Therefore add the non HTM value for
> completeness.
>
> Fixes: 0eb3726ebcf1 ("test/hash: add test for read/write concurrency")
>
> Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
> ---
[Wang, Yipeng] Thanks for the patch!
Acked-by: Yipeng Wang <yipeng1.wang@intel.com>
next prev parent reply other threads:[~2022-05-10 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 11:57 Stanislaw Kardach
2022-05-10 22:09 ` Wang, Yipeng1 [this message]
2022-05-11 11:56 ` 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=CO1PR11MB51723FFC4433972B58D145FAC3C99@CO1PR11MB5172.namprd11.prod.outlook.com \
--to=yipeng1.wang@intel.com \
--cc=Frank.Zhao@starfivetech.com \
--cc=dev@dpdk.org \
--cc=kda@semihalf.com \
--cc=mw@semihalf.com \
--cc=sam.grove@sifive.com \
--cc=upstream@semihalf.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 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).