From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"iryzhov@nfware.com" <iryzhov@nfware.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: make Tx scheduling xstats names compliant
Date: Sun, 22 Nov 2020 12:59:22 +0000 [thread overview]
Message-ID: <DM6PR12MB27487258BD0EC7DA180A7CFDCFFD0@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1605813504-19746-1-git-send-email-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Sent: Thursday, November 19, 2020 9:18 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-Thomas
> Monjalon <thomas@monjalon.net>; iryzhov@nfware.com
> Subject: [PATCH] net/mlx5: make Tx scheduling xstats names compliant
>
> xstats names for Tx packet scheduling should be compliant with [1]
>
> [1]
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.d
> pdk.org%2Fguides%2Fprog_guide%2Fpoll_mode_drv.html%3Fhighlight%3Dx
> stats%23extended-statistics-
> api&data=04%7C01%7Crasland%40nvidia.com%7C5991495fa463491652b
> 608d88cbff2c4%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C63741
> 4103323638044%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC
> JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uGX
> tUteavgLxrXenPedgrToUKTjm%2B5zUkwTXEaOd3%2BQ%3D&reserved
> =0
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_txpp.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-11-22 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 19:18 Viacheslav Ovsiienko
2020-11-22 12:59 ` Raslan Darawsheh [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=DM6PR12MB27487258BD0EC7DA180A7CFDCFFD0@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=iryzhov@nfware.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--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).