Linux s390 Architecture development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sabrina Dubroca" <sd@queasysnail.net>
Cc: linux-s390@vger.kernel.org,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH net-next v2 1/2] tls: remove tls_toe and the related driver
Date: Fri, 12 Jun 2026 10:21:51 +0000	[thread overview]
Message-ID: <20260612102151.D782D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <1f30e73275c07bf879f547589872d0916025a52e.1781165969.git.sd@queasysnail.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The cxgb4 driver continues to reserve MSI-X vectors and hardware queues for inline TLS offload even though the chtls driver has been removed.
--

commit fe56f0d87d512a0eea1f91c98873fd22553c6faf
Author: Sabrina Dubroca <sd@queasysnail.net>

tls: remove tls_toe and the related driver

This commit removes the tls_toe feature and its single user, the chelsio
chtls driver. These components have been unmaintained and bypass most of
the networking stack.

> diff --git a/drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c b/drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c
> index 6df98fca932f7..9e2c2fa16d7a5 100644
> --- a/drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c
> +++ b/drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c
> @@ -6795,8 +6795,7 @@ static int init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
>  						   NETIF_F_TSO | NETIF_F_TSO6;
>  
>  			netdev->hw_features |= NETIF_F_GSO_UDP_TUNNEL |
> -					       NETIF_F_GSO_UDP_TUNNEL_CSUM |
> -					       NETIF_F_HW_TLS_RECORD;
> +					       NETIF_F_GSO_UDP_TUNNEL_CSUM;

[Severity: Medium]
Since the chtls driver is being removed, should we also remove the 
FW_CAPS_CONFIG_TLS_INLINE capability check in get_caps() within the same file?

drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:get_caps() {
    ...
		if (ntohs(caps_cmd.cryptocaps) &
		    FW_CAPS_CONFIG_TLS_INLINE) {
			params[0] = FW_PARAM_PFVF(TLS_START);
			params[1] = FW_PARAM_PFVF(TLS_END);
			ret = t4_query_params(adap, adap->mbox, adap->pf, 0,
					      2, params, val);
			if (ret < 0)
				goto bye;
			adap->vres.key.start = val[0];
			adap->vres.key.size = val[1] - val[0] + 1;
			adap->num_uld += 1;
		}
    ...
}

Leaving this check in place causes the driver to increment adap->num_uld when
the firmware advertises TLS inline offload. This unconditionally reserves MSI-X
vectors and offload queues in cfg_queues() for a ULD that no longer exists in
the kernel.

Does this waste hardware queues and MSI-X vectors, potentially reducing the
number of queues available for the main Ethernet interface?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1781165969.git.sd@queasysnail.net?part=1

      parent reply	other threads:[~2026-06-12 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1781165969.git.sd@queasysnail.net>
2026-06-11 10:21 ` [PATCH net-next v2 1/2] tls: remove tls_toe and the related driver Sabrina Dubroca
2026-06-11 11:31   ` Eric Dumazet
2026-06-12 10:21   ` sashiko-bot [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=20260612102151.D782D1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sd@queasysnail.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