mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel Zahka" <daniel.zahka@gmail.com>
To: "Harshitha Ramamurthy" <hramamurthy@google.com>,
	"Daniel Zahka" <daniel.zahka@gmail.com>
Cc: "Alexander Duyck" <alexanderduyck@fb.com>,
	"Jakub Kicinski" <kuba@kernel.org>, <kernel-team@meta.com>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 3/4] eth: mpnic: set Rx buffer minimums using page size and mtu
Date: Mon, 05 Oct 2026 07:15:49 -0400	[thread overview]
Message-ID: <DLWV19JLLG9C.17IJGD2C6XDK4@gmail.com> (raw)
In-Reply-To: <CAEAWyHfRqE5wJTi7jq6LAK4-+i0bTFGzVU_HByEGUJJ7sGcGbA@mail.gmail.com>

On Fri Oct 2, 2026 at 8:50 PM EDT, Harshitha Ramamurthy wrote:
> On Thu, Oct 1, 2026 at 9:46 AM Daniel Zahka <daniel.zahka@gmail.com> wrote:
>>
>> Set buffer based drop thresholds in the Rx path based on page size and
>> the max MTU supported. The device will drop packets if it does not have
>> at least the minimum number of completely unused buffer descriptors
>> available.
>>
>> These thresholds are currently set to 17 BDs for both HPQ and PPQ. These
>
> nit: if there is a v2, it would be helpful for review if terms like
> PPQ/HPQ were expanded here.
>

Thanks for taking a look. The acronyms are:
HPQ: header page queue
PPQ: payload page queue

  reply	other threads:[~2026-10-05 11:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 16:38 [PATCH net-next 0/4] mpnic: add NAPI buffer depletion check Daniel Zahka
2026-10-01 16:38 ` [PATCH net-next 1/4] eth: mpnic: use WRITE_ONCE() for BDQ head and tail updates Daniel Zahka
2026-10-01 16:38 ` [PATCH net-next 2/4] eth: mpnic: add a service task Daniel Zahka
2026-10-01 16:39 ` [PATCH net-next 3/4] eth: mpnic: set Rx buffer minimums using page size and mtu Daniel Zahka
2026-10-03  0:50   ` Harshitha Ramamurthy
2026-10-05 11:15     ` Daniel Zahka [this message]
2026-10-01 16:39 ` [PATCH net-next 4/4] eth: mpnic: add a NAPI depletion check Daniel Zahka
2026-10-03  0:53   ` Harshitha Ramamurthy
2026-10-05 11:42     ` Daniel Zahka
2026-10-01 16:45 ` [PATCH net-next 0/4] mpnic: add NAPI buffer " netdev-bot+sinfo
2026-10-01 18:26   ` Daniel Zahka
2026-10-03  0:54 ` Harshitha Ramamurthy
2026-10-06  0:00 ` patchwork-bot+netdevbpf

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=DLWV19JLLG9C.17IJGD2C6XDK4@gmail.com \
    --to=daniel.zahka@gmail.com \
    --cc=alexanderduyck@fb.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hramamurthy@google.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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
all inboxes | Powered by JetHome®