DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Joshua Washington <joshwash@google.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Jeroen de Borst <jeroendb@google.com>,
	Rushil Gupta <rushilg@google.com>
Cc: dev@dpdk.org, Harshitha Ramamurthy <hramamurthy@google.com>
Subject: Re: [PATCH v2] net/gve: change QPLs to be queue resources
Date: Fri, 5 Jul 2024 22:13:01 +0100	[thread overview]
Message-ID: <33d51b5c-a552-42d8-bea4-1713d2fe6ed5@amd.com> (raw)
In-Reply-To: <20240613235331.850227-1-joshwash@google.com>

On 6/14/2024 12:53 AM, Joshua Washington wrote:
> Prior to this change, queue page lists (QPLs) were kept as device
> resources, being stored in the gve_priv struct. This does not make
> sense because each QPL inherently belongs to a single queue.
> 
> This change moves all QPL resources into the queues themselves, and
> couples QPL allocation/registration and de-registration/deallocation
> with the queue creation and destruction processes, respectively. Before
> this change, QPL structs part of gve_priv were allocated as part of
> driver initialization, which similarly does not make sense.
> 
> Signed-off-by: Joshua Washington <joshwash@google.com>
> Reviewed-by: Harshitha Ramamurthy <hramamurthy@google.com>
> Reviewed-by: Rushil Gupta <rushilg@google.com>
>

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

(fixed .mailmap while fixing, it should list all emails in the git
history, first one being primary one.)

      reply	other threads:[~2024-07-05 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 22:59 [PATCH] " Joshua Washington
2024-06-13 23:49 ` [PATCH v2] " Joshua Washington
2024-06-13 23:53 ` Joshua Washington
2024-07-05 21:13   ` 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=33d51b5c-a552-42d8-bea4-1713d2fe6ed5@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=hramamurthy@google.com \
    --cc=jeroendb@google.com \
    --cc=joshwash@google.com \
    --cc=rushilg@google.com \
    --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).