DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Guo, Junfeng" <junfeng.guo@intel.com>,
	Rushil Gupta <rushilg@google.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Joshua Washington <joshwash@google.com>
Subject: Re: [PATCH] net/gve: Refill all descriptors that were consumed
Date: Thu, 21 Sep 2023 17:37:45 +0100	[thread overview]
Message-ID: <c85d49b9-4be1-4c99-b129-9735f67387ba@amd.com> (raw)
In-Reply-To: <DM6PR11MB3723E6B73F20274A2DE5DE0DE7F6A@DM6PR11MB3723.namprd11.prod.outlook.com>

On 9/15/2023 3:28 AM, Guo, Junfeng wrote:
>> -----Original Message-----
>> From: Rushil Gupta <rushilg@google.com>
>> Sent: Friday, September 15, 2023 04:52
>> To: Zhang, Qi Z <qi.z.zhang@intel.com>; ferruh.yigit@amd.com
>> Cc: Guo, Junfeng <junfeng.guo@intel.com>; dev@dpdk.org; Rushil Gupta
>> <rushilg@google.com>; Joshua Washington <joshwash@google.com>
>> Subject: [PATCH] net/gve: Refill all descriptors that were consumed
>>
>> Refill all consumed descriptors instead of refilling a set amount of
>> descriptors everytime. Also, lower the rx-free-thresh to refill more
>> aggressively. This yields in fewer packet drops for DQO queue format.
>>
>> Signed-off-by: Rushil Gupta <rushilg@google.com>
>> Reviewed-by: Joshua Washington <joshwash@google.com>
> 
> Acked-by: Junfeng Guo <junfeng.guo@intel.com>
>

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2023-09-21 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 20:52 Rushil Gupta
2023-09-15  2:28 ` Guo, Junfeng
2023-09-21 16:37   ` Ferruh Yigit [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=c85d49b9-4be1-4c99-b129-9735f67387ba@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=joshwash@google.com \
    --cc=junfeng.guo@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rushilg@google.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).