mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* i40e: How the packets will be processed when status_error_len is 0
@ 2025-05-13  4:03 Haifeng Xu
  2025-05-13  6:13 ` Jason Xing
  0 siblings, 1 reply; 3+ messages in thread
From: Haifeng Xu @ 2025-05-13  4:03 UTC (permalink / raw)
  To: Tony Nguyen, Jesse Brandeburg, David S. Miller, Eric Dumazet,
	Jakub Kicinski, Paolo Abeni, intel-wired-lan, netdev,
	linux-kernel

Hi all,

	If the packets arrive at the rx and then raise soft irq to handle it, but in i40e_clean_rx_irq, status_error_len is 0 and return.
	The data isn't fetchted from the rx buffer, so the how the packets arrive at the rx will be processed?
	
	FYI, the every rx/tx queue has been bounded to one cpu(64 queues, 64 cpus).

Thanks!

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: i40e: How the packets will be processed when status_error_len is 0
  2025-05-13  4:03 i40e: How the packets will be processed when status_error_len is 0 Haifeng Xu
@ 2025-05-13  6:13 ` Jason Xing
  2025-05-13  6:23   ` Haifeng Xu
  0 siblings, 1 reply; 3+ messages in thread
From: Jason Xing @ 2025-05-13  6:13 UTC (permalink / raw)
  To: Haifeng Xu
  Cc: Tony Nguyen, Jesse Brandeburg, David S. Miller, Eric Dumazet,
	Jakub Kicinski, Paolo Abeni, intel-wired-lan, netdev,
	linux-kernel

On Tue, May 13, 2025 at 12:08 PM Haifeng Xu <haifeng.xu@shopee.com> wrote:
>
> Hi all,
>
>         If the packets arrive at the rx and then raise soft irq to handle it, but in i40e_clean_rx_irq, status_error_len is 0 and return.

Directly "return"? What version of I40E are you looking at?

>         The data isn't fetchted from the rx buffer, so the how the packets arrive at the rx will be processed?

In i40e_clean_rx_irq(), packets are one by one constructed into the
sk_buff and then passed to the stack by napi_gro_receive().

AFAIK, common drivers implement nearly the same scenario.


Thanks,
Jason


>
>         FYI, the every rx/tx queue has been bounded to one cpu(64 queues, 64 cpus).
>
> Thanks!
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: i40e: How the packets will be processed when status_error_len is 0
  2025-05-13  6:13 ` Jason Xing
@ 2025-05-13  6:23   ` Haifeng Xu
  0 siblings, 0 replies; 3+ messages in thread
From: Haifeng Xu @ 2025-05-13  6:23 UTC (permalink / raw)
  To: Jason Xing
  Cc: Tony Nguyen, Jesse Brandeburg, David S. Miller, Eric Dumazet,
	Jakub Kicinski, Paolo Abeni, intel-wired-lan, netdev,
	linux-kernel



On 2025/5/13 14:13, Jason Xing wrote:
> On Tue, May 13, 2025 at 12:08 PM Haifeng Xu <haifeng.xu@shopee.com> wrote:
>>
>> Hi all,
>>
>>         If the packets arrive at the rx and then raise soft irq to handle it, but in i40e_clean_rx_irq, status_error_len is 0 and return.
> 
> Directly "return"? What version of I40E are you looking at?

stable kenrel 5.15.162,

i40e_clean_rx_irq
...
	qword = le64_to_cpu(rx_desc->wb.qword1.status_error_len);
	...
	size = (qword & I40E_RXD_QW1_LENGTH_PBUF_MASK) >>
		       I40E_RXD_QW1_LENGTH_PBUF_SHIFT;
	if (!size)
		break;
...

if status_error_len is 0, the i40e_clean_rx_irq returns 0.
> 
>>         The data isn't fetchted from the rx buffer, so the how the packets arrive at the rx will be processed?
> 
> In i40e_clean_rx_irq(), packets are one by one constructed into the
> sk_buff and then passed to the stack by napi_gro_receive().
> 
> AFAIK, common drivers implement nearly the same scenario.
> 
> 
> Thanks,
> Jason
> 
> 
>>
>>         FYI, the every rx/tx queue has been bounded to one cpu(64 queues, 64 cpus).
>>
>> Thanks!
>>


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-05-13  6:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-05-13  4:03 i40e: How the packets will be processed when status_error_len is 0 Haifeng Xu
2025-05-13  6:13 ` Jason Xing
2025-05-13  6:23   ` Haifeng Xu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®