public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Damato <jdamato@fastly.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	alexanderduyck@fb.com
Subject: Re: [PATCH net-next 3/3] eth: fbnic: support ring size configuration
Date: Thu, 6 Mar 2025 10:05:08 -0800	[thread overview]
Message-ID: <Z8nj1Aq7TC3V6WOc@LQ3V64L9R2> (raw)
In-Reply-To: <20250306145150.1757263-4-kuba@kernel.org>

On Thu, Mar 06, 2025 at 06:51:50AM -0800, Jakub Kicinski wrote:
> Support ethtool -g / -G. Leverage the code added for -l / -L
> to alloc / stop / start / free.
> 
> Check parameters against HW min/max but also our own min/max.
> Min HW queue is 16 entries, we can't deal with TWQs that small
> because of the queue waking logic. Add similar contraint on RCQ
> for symmetry.
> 
> We need 3 sizes on Rx, as the NIC does header-data split two separate
> buffer pools:
>   (1) head page ring    - how many empty pages we post for headers
>   (2) payload page ring - how many empty pages we post for payloads
>   (3) completion ring   - where NIC produces the Rx descriptors
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> v0.2:
>  - trim unused defines
>  - add comment
>  - add info to commit msg
>  - add extack
> ---
>  drivers/net/ethernet/meta/fbnic/fbnic_txrx.h  |  13 +++
>  .../net/ethernet/meta/fbnic/fbnic_ethtool.c   | 109 ++++++++++++++++++
>  2 files changed, 122 insertions(+)

Looked at this for a bit and read a bit more of fbnic. I obviously
know nothing about this device but nothing jumped out to me while
reading the patch:

Acked-by: Joe Damato <jdamato@fastly.com>

  reply	other threads:[~2025-03-06 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 14:51 [PATCH net-next 0/3] eth: fbnic: support ring size configuration Jakub Kicinski
2025-03-06 14:51 ` [PATCH net-next 1/3] eth: fbnic: link NAPIs to page pools Jakub Kicinski
2025-03-06 17:12   ` Joe Damato
2025-03-06 14:51 ` [PATCH net-next 2/3] eth: fbnic: fix typo in compile assert Jakub Kicinski
2025-03-06 17:13   ` Joe Damato
2025-03-06 14:51 ` [PATCH net-next 3/3] eth: fbnic: support ring size configuration Jakub Kicinski
2025-03-06 18:05   ` Joe Damato [this message]
2025-03-08  3:50 ` [PATCH net-next 0/3] " 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=Z8nj1Aq7TC3V6WOc@LQ3V64L9R2 \
    --to=jdamato@fastly.com \
    --cc=alexanderduyck@fb.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@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