DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Rong, Leyi" <leyi.rong@intel.com>, "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ice: enlarge ice RXQ rearm thresh to 64
Date: Tue, 12 Jan 2021 05:11:59 +0000	[thread overview]
Message-ID: <7190e3e99b3942c1b2858fee5f9d31ee@intel.com> (raw)
In-Reply-To: <20210106053548.67341-1-leyi.rong@intel.com>

> -----Original Message-----
> From: Rong, Leyi <leyi.rong@intel.com>
> Sent: Wednesday, January 6, 2021 1:36 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Cc: dev@dpdk.org; Rong, Leyi <leyi.rong@intel.com>
> Subject: [PATCH] net/ice: enlarge ice RXQ rearm thresh to 64
> We observe performance drop on ice AVX512 data path after stop and start by
> using testpmd.
> As CPU polling is faster in AVX512 path, L3 contested accesses is intensified
> when rxrearm_start is a random value after testpmd stop/start.
> Enlarge ICE_RXQ_REARM_THRESH to 64 to ease the contested asscesses and fix
> the performance drop issue.
> Signed-off-by: Leyi Rong <leyi.rong@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel after add cc:stable tag.


      reply	other threads:[~2021-01-12  5:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06  5:35 Leyi Rong
2021-01-12  5:11 ` Zhang, Qi Z [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7190e3e99b3942c1b2858fee5f9d31ee@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=leyi.rong@intel.com \
    --cc=wenzhuo.lu@intel.com \


* 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).