From: Thomas Monjalon <thomas@monjalon.net>
To: Shun Hao <shunh@nvidia.com>
Cc: orika@nvidia.com, viacheslavo@nvidia.com, matan@nvidia.com,
dev@dpdk.org, rasland@nvidia.com
Subject: Re: [dpdk-dev] [PATCH v1 0/2] Fix Meter Hierarchy related issues
Date: Wed, 04 Aug 2021 11:26:12 +0200 [thread overview]
Message-ID: <10306511.eqstsTDq79@thomas> (raw)
In-Reply-To: <20210804072647.2077832-1-shunh@nvidia.com>
04/08/2021 09:26, Shun Hao:
> 1. fix the wrong flow statistics when flow contains both count/meter.
> 2. fix the wrong meter domain access when meters in hierarchy support
> different domains.
>
> Shun Hao (2):
> net/mlx5: fix meter flow counter traslation
> net/mlx5: fix domains detection in meter hierarchy
Applied, thanks.
prev parent reply other threads:[~2021-08-04 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 7:26 Shun Hao
2021-08-04 7:26 ` [dpdk-dev] [PATCH v1 1/2] net/mlx5: fix meter flow counter traslation Shun Hao
2021-08-04 7:26 ` [dpdk-dev] [PATCH v1 2/2] net/mlx5: fix domains detection in meter hierarchy Shun Hao
2021-08-04 9:26 ` 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=10306511.eqstsTDq79@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=shunh@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 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).