Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, kuba@kernel.org, gospo@broadcom.com
Subject: [PATCH net-next 0/2] bnxt_en: Increase maximum RX ring size when jumbo ring is unused
Date: Mon,  2 Aug 2021 10:52:37 -0400	[thread overview]
Message-ID: <1627915959-1648-1-git-send-email-michael.chan@broadcom.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 831 bytes --]

The RX jumbo ring is automatically enabled when HW GRO/LRO is enabled or
when the MTU exceeds the page size.  The RX jumbo ring provides a lot
more RX buffer space when it is in use.  When the RX jumbo ring is not
in use, some users report that the current maximum of 2K buffers is
too limiting.  This patchset increases the maximum to 8K buffers when
the RX jumbo ring is not used.  The default RX ring size is unchanged
at 511.

Michael Chan (2):
  bnxt_en: Don't use static arrays for completion ring pages.
  bnxt_en: Increase maximum RX ring size if jumbo ring is not used.

 drivers/net/ethernet/broadcom/bnxt/bnxt.c     | 75 ++++++++++++++++++-
 drivers/net/ethernet/broadcom/bnxt/bnxt.h     | 17 +++--
 .../net/ethernet/broadcom/bnxt/bnxt_ethtool.c |  9 ++-
 3 files changed, 90 insertions(+), 11 deletions(-)

-- 
2.18.1


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]

             reply	other threads:[~2021-08-02 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 14:52 Michael Chan [this message]
2021-08-02 14:52 ` [PATCH net-next 1/2] bnxt_en: Don't use static arrays for completion ring pages Michael Chan
2021-08-02 14:52 ` [PATCH net-next 2/2] bnxt_en: Increase maximum RX ring size if jumbo ring is not used Michael Chan
2021-08-03 11:50 ` [PATCH net-next 0/2] bnxt_en: Increase maximum RX ring size when jumbo ring is unused 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=1627915959-1648-1-git-send-email-michael.chan@broadcom.com \
    --to=michael.chan@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=gospo@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --subject='Re: [PATCH net-next 0/2] bnxt_en: Increase maximum RX ring size when jumbo ring is unused' \
    /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

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).