Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: javen_xu@realsil.com.cn
Cc: Jakub Kicinski <kuba@kernel.org>,
	hkallweit1@gmail.com, nic_swsd@realtek.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v10 5/7] r8169: add support and enable rss
Date: Mon, 10 Aug 2026 14:31:44 -0700	[thread overview]
Message-ID: <20260810213144.854057-1-kuba@kernel.org> (raw)
In-Reply-To: <20260803021305.488-6-javen_xu@realsil.com.cn>

This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
---
r8169: add support and enable rss

This patch adds support and enables Receive Side Scaling (RSS) for RTL8127.
It configures RSS keys, redirection tables, and introduces support for
parsing RSS-specific RX descriptors.

> diff --git a/drivers/net/ethernet/realtek/r8169_main.c b/drivers/net/ethernet/realtek/r8169_main.c
> --- a/drivers/net/ethernet/realtek/r8169_main.c
> +++ b/drivers/net/ethernet/realtek/r8169_main.c
[ ... ]
> @@ -4920,27 +5123,87 @@ static inline int rtl8169_fragmented_frame(u32 status)
>  	return (status & (FirstFrag | LastFrag)) != (FirstFrag | LastFrag);
>  }
>  
> -static inline void rtl8169_rx_csum(struct sk_buff *skb,
> +static inline void rtl8169_rx_hash(struct rtl8169_private *tp,
> +				   struct RxDesc *desc,
> +				   struct sk_buff *skb)
[ ... ]
> +static inline void rtl8169_rx_csum(struct rtl8169_private *tp,
> +				   struct sk_buff *skb,
>  				   u32 opts1)
>  {
> -	u32 status = opts1 & (RxProtoMask | RxCSFailMask);
> +	bool csum_ok = false;
> +
> +	switch (tp->init_rx_desc_type) {
> +	case RX_DESC_TYPE_RSS:
> +		if (((opts1 & RX_TCPT_DESC_RSS) && !(opts1 & RX_TCPF_DESC_RSS)) ||
> +		    ((opts1 & RX_UDPT_DESC_RSS) && !(opts1 & RX_UDPF_DESC_RSS)))
> +			csum_ok = true;
> +		break;
> +	default:
> +		u32 status = opts1 & (RxProtoMask | RxCSFailMask);

[Severity: Low]
Will this compile under standard C? Declaring a variable immediately
following a label (default:) is a syntax error in C unless it is wrapped in
a block.

>  
> -	if (status == RxProtoTCP || status == RxProtoUDP)
> +		if (status == RxProtoTCP || status == RxProtoUDP)
> +			csum_ok = true;
> +		break;
> +	}
> +
> +	if (csum_ok)
>  		skb->ip_summed = CHECKSUM_UNNECESSARY;
>  	else
>  		skb_checksum_none_assert(skb);
>  }
[ ... ]
>  static bool rtl8169_check_rx_desc_error(struct net_device *dev,
>  					struct rtl8169_private *tp,
>  					u32 status)
>  {
> -	if (unlikely(status & RxRES)) {
> -		if (status & (RxRWT | RxRUNT))
> -			dev->stats.rx_length_errors++;
> -		if (status & RxCRC)
> -			dev->stats.rx_crc_errors++;
> -		return true;
> +	switch (tp->init_rx_desc_type) {
> +	case RX_DESC_TYPE_RSS:
> +		if (unlikely(status & RX_RES_RSS)) {
> +			if (status & RX_RUNT_RSS)
> +				dev->stats.rx_length_errors++;
> +			if (status & RX_CRC_RSS)
> +				dev->stats.rx_crc_errors++;

[Severity: Medium]
Can these direct increments to dev->stats cause lost updates?

Now that RSS is enabled, multiple RX queues can trigger NAPI polling
concurrently on different CPUs. If multiple queues receive errored packets
simultaneously, they will race to read-modify-write these global stat
counters.

> +			return true;
> +		}
> +		break;
> +	default:
> +		if (unlikely(status & RxRES)) {
> +			if (status & (RxRWT | RxRUNT))
> +				dev->stats.rx_length_errors++;
> +			if (status & RxCRC)
> +				dev->stats.rx_crc_errors++;
> +			return true;
> +		}
> +		break;
>  	}
>  	return false;
>  }
[ ... ]
> @@ -4977,7 +5240,8 @@ static int rtl_rx(struct net_device *dev, struct rtl8169_private *tp,
>  
>  			if (!(dev->features & NETIF_F_RXALL))
>  				goto release_descriptor;
> -			else if (status & RxRWT || !(status & (RxRUNT | RxCRC)))
> -				goto release_descriptor;
> +			if ((status & RxRWT || !(status & (RxRUNT | RxCRC))) &&
> +			    tp->init_rx_desc_type == RX_DESC_TYPE_DEFAULT)
> +				goto release_descriptor;
>  		}

[Severity: High]
Does this bypass the drop logic for fatal errors when RSS and RXALL are
both enabled?

If the hardware receives a fatally errored packet while RSS is enabled,
the descriptor type check (tp->init_rx_desc_type == RX_DESC_TYPE_DEFAULT)
prevents the code from taking the goto release_descriptor path. This could
cause the driver to process frames with corrupted length fields or 
uninitialized memory.

>  
> @@ -5010,10 +5274,12 @@ static int rtl_rx(struct net_device *dev, struct rtl8169_private *tp,

  reply	other threads:[~2026-08-10 21:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  2:12 [PATCH net-next v10 0/7] r8169: add RSS support for RTL8127 javen
2026-08-03  2:12 ` [PATCH net-next v10 1/7] r8169: add support for multi irqs javen
2026-08-03  2:13 ` [PATCH net-next v10 2/7] r8169: refactor RX path to prepare for multi-queue javen
2026-08-10 21:26   ` Jakub Kicinski
2026-08-03  2:13 ` [PATCH net-next v10 3/7] r8169: add support for new interrupt mapping javen
2026-08-10 21:29   ` Jakub Kicinski
2026-08-03  2:13 ` [PATCH net-next v10 4/7] r8169: enable " javen
2026-08-10 21:31   ` Jakub Kicinski
2026-08-03  2:13 ` [PATCH net-next v10 5/7] r8169: add support and enable rss javen
2026-08-10 21:31   ` Jakub Kicinski [this message]
2026-08-10 21:38   ` Jakub Kicinski
2026-08-03  2:13 ` [PATCH net-next v10 6/7] r8169: move struct ethtool_ops javen
2026-08-03  2:13 ` [PATCH net-next v10 7/7] r8169: support setting rx queue numbers via ethtool javen
2026-08-10 21:41   ` Jakub Kicinski

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=20260810213144.854057-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=javen_xu@realsil.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --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