DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Joshua Washington <joshwash@google.com>
Cc: dev@dpdk.org, Rushil Gupta <rushilg@google.com>,
	Harshitha Ramamurthy <hramamurthy@google.com>
Subject: Re: [PATCH 0/4] gve GQ ring size modification
Date: Fri, 19 Jul 2024 19:59:14 +0100	[thread overview]
Message-ID: <5f45f944-3646-41c9-b00f-19690e705c2a@amd.com> (raw)
In-Reply-To: <20240717175619.3159026-1-joshwash@google.com>

On 7/17/2024 6:56 PM, Joshua Washington wrote:
> This patch series adds the abiltiy to modify the ring size when using
> the GQ queue format for the GVE driver. Before this change, the GQ
> driver supported only 1024 descriptors in a ring. With this change, ring
> sizes can be as low or has as is specfied by the device. If the device
> does not specify limits, the minimum ring size is fixed at 512
> descriptors for RX and 256 descriptor for TX, while the maximum ring
> size is fixed at 1024 for both RX and TX.
> 
> Limitations:
>   The ring size must be a power of two.
> 
> The DQ queue format should remain unaffected by this change.
> 
> Joshua Washington (4):
>   net/gve: add ring size device option
>   net/gve: remove explicit field for Rx pages per QPL
>   net/gve: add min ring size support
>   net/gve: add ability to modify ring size in GQ format
>

Series applied to dpdk-next-net/main, thanks.

      parent reply	other threads:[~2024-07-19 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 17:56 Joshua Washington
2024-07-17 17:56 ` [PATCH 1/4] net/gve: add ring size device option Joshua Washington
2024-07-17 17:56 ` [PATCH 2/4] net/gve: remove explicit field for Rx pages per QPL Joshua Washington
2024-07-17 17:56 ` [PATCH 3/4] net/gve: add min ring size support Joshua Washington
2024-07-17 17:56 ` [PATCH 4/4] net/gve: add ability to modify ring size in GQ format Joshua Washington
2024-07-19 18:59 ` 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=5f45f944-3646-41c9-b00f-19690e705c2a@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=hramamurthy@google.com \
    --cc=joshwash@google.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).