DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rasesh Mody <rmody@marvell.com>
To: Shahed Shaikh <shshaikh@marvell.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/qede: fix performance bottleneck in Rx path
Date: Fri, 18 Jan 2019 17:15:21 +0000	[thread overview]
Message-ID: <BYAPR18MB28386C5DB9B89051C0390CA9B59C0@BYAPR18MB2838.namprd18.prod.outlook.com> (raw)
In-Reply-To: <BYAPR18MB2696B332DE4CBCC534009154D39C0@BYAPR18MB2696.namprd18.prod.outlook.com>

>From: Shahed Shaikh
>Sent: Friday, January 18, 2019 8:13 AM
>
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yigit@intel.com>
>> Sent: Friday, January 18, 2019 8:11 PM
>> To: Shahed Shaikh <shshaikh@marvell.com>; dev@dpdk.org
>> Cc: stable@dpdk.org; Rasesh Mody <rmody@marvell.com>; Thomas
>Monjalon
>> <thomas@monjalon.net>
>> Subject: [EXT] Re: [dpdk-dev] [PATCH 1/2] net/qede: fix performance
>> bottleneck in Rx path
>>
>>
>> ----------------------------------------------------------------------
>> On 1/18/2019 2:41 PM, Ferruh Yigit wrote:
>> > On 1/18/2019 10:29 AM, Shahed Shaikh wrote:
>> >> Allocating replacement buffer per received packet is expensive.
>> >> Instead, process received packets first and allocate replacement
>> >> buffers in bulk later.
>> >>
>> >> This improves performance by ~25% in terms of PPS on AMD platforms.
>> >>
>> >> Fixes: 2ea6f76aff40 ("qede: add core driver")
>> >> Cc: stable@dpdk.org
>> >>
>> >> Signed-off-by: Shahed Shaikh <shshaikh@marvell.com>
>> >
>> > Hi Shahed,
>> >
>> > This patch has been sent same day of the RC3, very close to the
>> > actual release, and updating data path of the driver, so not a trivial patch.
>> >
>> > Although I tend to accept driver patches late in process this one
>> > was too late, you won't have proper time to fix if any errors
>> > detected, but also I can see it has a good amount performance effect.
>> >
>> > I would like to explicitly ask if you are willing to take the risk.
>> > If answer is yes, please also be sure to get Rasesh's ack.
>
>Hi Ferruh,
>
>We have done thorough regression testing with this series and would like to
>get this included in 19.02.
>Please consider this series.
>
>Rasesh,
>Please ack this series.

Hi Ferruh, Thomas,

Both the patches in the series are acked and well tested against 19.02 tree.

Thanks!
-Rasesh
>
>Thanks,
>Shahed
>>
>> cc'ed Thomas.

  reply	other threads:[~2019-01-18 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 16:13 Shahed Shaikh
2019-01-18 17:15 ` Rasesh Mody [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-18 10:29 Shahed Shaikh
2019-01-18 14:41 ` Ferruh Yigit
2019-01-18 14:41   ` Ferruh Yigit
2019-01-18 16:57 ` Rasesh Mody
2019-01-18 23:39   ` Thomas Monjalon

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=BYAPR18MB28386C5DB9B89051C0390CA9B59C0@BYAPR18MB2838.namprd18.prod.outlook.com \
    --to=rmody@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=shshaikh@marvell.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).