From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Asaf Penso <asafp@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>,
Feifei Wang <Feifei.Wang2@arm.com>, nd <nd@arm.com>,
subhim@nvidia.com
Subject: Re: Issues with MLX NIC perf report
Date: Tue, 17 Jan 2023 10:52:54 +0100 [thread overview]
Message-ID: <2596891.BjyWNHgNrj@thomas> (raw)
In-Reply-To: <DBAPR08MB5814B6FD9558C7D5F12B6D2D98FC9@DBAPR08MB5814.eurprd08.prod.outlook.com>
11/01/2023 23:06, Honnappa Nagarahalli:
> Hello,
> I am looking at [1]. In Chapter 8, Table 18, 'Test Configuration' mentions using 16 cores. However, in section 8.1, Table 19, 'Command Line' is using 12 cores. Appreciate correcting this.
>
> I assume the command line is the correct one.
Looks like you are right.
The affected reports will be fixed.
Thanks for reporting.
prev parent reply other threads:[~2023-01-17 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 22:06 Issues with MLX NIC perf report Honnappa Nagarahalli
2023-01-17 9:52 ` Thomas Monjalon [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=2596891.BjyWNHgNrj@thomas \
--to=thomas@monjalon.net \
--cc=Feifei.Wang2@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=subhim@nvidia.com \
--cc=viacheslavo@nvidia.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.