All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Taehee Yoo <ap420073@gmail.com>
Cc: Michael Chan <michael.chan@broadcom.com>,
	David Wei <dw@davidwei.uk>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Mina Almasry <almasrymina@google.com>,
	Netdev <netdev@vger.kernel.org>
Subject: Re: Question about TPA/HDS feature of bnxt_en
Date: Tue, 13 Aug 2024 18:17:08 -0700	[thread overview]
Message-ID: <20240813181708.5ff6f5de@kernel.org> (raw)
In-Reply-To: <CAMArcTXtKGp24EAd6xUva0x=81agVcNkm9rMos+CdEh6V_Ae4g@mail.gmail.com>

On Tue, 13 Aug 2024 19:42:51 +0900 Taehee Yoo wrote:
> Hi,
> I'm currently testing the device memory TCP feature with the bnxt_en
> driver because Broadcom NICs support TPA/HDS, which is a mandatory
> feature for the devmem TCP.
> But it doesn't work for short-sized packets(under 300?)
> So, the devmem TCP stops or errors out if it receives non-header-splitted skb.
> 
> I hope the bnxt_en driver or firmware has options that force TPA to
> work for short-sized packets.
> So, Can I get any condition information on TPA?

I don't have any non-public info but look around the driver for
rx_copy_thresh, it seems to be sent to FW. I wonder if setting
it to 1 or 0 would work. Especially this:

static int bnxt_hwrm_vnic_set_hds(struct bnxt *bp, struct bnxt_vnic_info *vnic)
...
		req->hds_threshold = cpu_to_le16(bp->rx_copy_thresh);

  reply	other threads:[~2024-08-14  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 10:42 Question about TPA/HDS feature of bnxt_en Taehee Yoo
2024-08-14  1:17 ` Jakub Kicinski [this message]
2024-08-14  2:08   ` Michael Chan
2024-08-14  7:51     ` Taehee Yoo
2024-08-14 17:17       ` Michael Chan
2024-08-15  9:06         ` Taehee Yoo
2024-08-14  7:27   ` Taehee Yoo

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=20240813181708.5ff6f5de@kernel.org \
    --to=kuba@kernel.org \
    --cc=almasrymina@google.com \
    --cc=ap420073@gmail.com \
    --cc=dw@davidwei.uk \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=somnath.kotur@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.