From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Ali Alnubani <alialnu@nvidia.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>
Subject: Re: [dts] [PATCH] tests/nic_single_core_perf: set burst and mbcache for ConnectX nics
Date: Fri, 25 Jun 2021 02:12:57 +0000 [thread overview]
Message-ID: <e4638825ccc84a89abce710ea1cf0442@intel.com> (raw)
In-Reply-To: <20210617155324.9192-1-alialnu@nvidia.com>
> -----Original Message-----
> From: Ali Alnubani <alialnu@nvidia.com>
> Sent: 2021年6月17日 23:53
> To: dts@dpdk.org; Tu, Lijuan <lijuan.tu@intel.com>
> Cc: dpdklab@iol.unh.edu
> Subject: [PATCH] tests/nic_single_core_perf: set burst and mbcache for
> ConnectX nics
>
> Setting burst and mbcache improves performance and reduces fluctuations.
>
> Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
Applied, thanks
prev parent reply other threads:[~2021-06-25 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 15:53 Ali Alnubani
2021-06-25 2:12 ` Tu, Lijuan [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=e4638825ccc84a89abce710ea1cf0442@intel.com \
--to=lijuan.tu@intel.com \
--cc=alialnu@nvidia.com \
--cc=dpdklab@iol.unh.edu \
--cc=dts@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).