DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Somnath Kotur <somnath.kotur@broadcom.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, ajit.khaparde@broadcom.com
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fixes in flow counter mgr
Date: Wed, 05 Aug 2020 22:03:03 +0200	[thread overview]
Message-ID: <5320795.Xbk6jbSQu1@thomas> (raw)
In-Reply-To: <20200803141219.5682-1-somnath.kotur@broadcom.com>

03/08/2020 16:12, Somnath Kotur:
> OVS-DPDK seems to set the reset bit for every flow query. Honor
> the bit by resetting the SW counter values after assigning them.
> Also set the 'hit' bit only if the counter value retrieved by HW
> is non-zero.
> While querying flow stats, use max possible entries in the fc table scan
> for valid entries instead of active entries as the active entry can be in
> any slot in the table.
> 
> This is a critical fix for OVS-DPDK flow aging.
> 
> Fixes: 306c2d28e247 ("net/bnxt: support count action in flow query")
> 
> Reviewed-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
> Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>

Tags must be in chronological order (Reviewed-by after Signed-off-by).

> ---
>  drivers/net/bnxt/tf_ulp/ulp_fc_mgr.c | 25 +++++++++++++++++--------
>  1 file changed, 17 insertions(+), 8 deletions(-)

That's not a small change.

The title does not convey the impact of the change.

Applied anyway because you insisted on the criticality.



      reply	other threads:[~2020-08-05 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 14:12 Somnath Kotur
2020-08-05 20:03 ` 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=5320795.Xbk6jbSQu1@thomas \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=somnath.kotur@broadcom.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).