DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bing Zhao <bingz@nvidia.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>, Ali Alnubani <alialnu@nvidia.com>
Subject: RE: [PATCH] common/mlx5: remove unneeded field when modify RQ table
Date: Thu, 18 Jul 2024 04:10:54 +0000	[thread overview]
Message-ID: <DM4PR12MB5184FC85927365F9BB9C005FD0AC2@DM4PR12MB5184.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUBNZHjar+feVfxRMskb_gnLDaxoPPYDTzK551vxmekoEQ@mail.gmail.com>

Hi Patrick,

It seems to be so. The patch is only for mlx5 slow path configuration. There is no reason that such change will impact the BRCM NIC performance.

Thanks.

BR. Bing

> -----Original Message-----
> From: Patrick Robb <probb@iol.unh.edu>
> Sent: Thursday, July 18, 2024 4:58 AM
> To: Bing Zhao <bingz@nvidia.com>
> Cc: Slava Ovsiienko <viacheslavo@nvidia.com>; dev@dpdk.org; Raslan
> Darawsheh <rasland@nvidia.com>; Ori Kam <orika@nvidia.com>; Dariusz
> Sosnowski <dsosnowski@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>;
> Matan Azrad <matan@nvidia.com>
> Subject: Re: [PATCH] common/mlx5: remove unneeded field when modify RQ
> table
> 
> External email: Use caution opening links or attachments
> 
> 
> Rerunning the CI Test for Broadcom Performance, which appears to be a
> false failure.

  reply	other threads:[~2024-07-18  4:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 16:37 Bing Zhao
2024-07-17 20:57 ` Patrick Robb
2024-07-18  4:10   ` Bing Zhao [this message]
2024-07-21 12:12 ` Raslan Darawsheh

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=DM4PR12MB5184FC85927365F9BB9C005FD0AC2@DM4PR12MB5184.namprd12.prod.outlook.com \
    --to=bingz@nvidia.com \
    --cc=alialnu@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=probb@iol.unh.edu \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@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).