lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sat, 01 Oct 2022 20:40:18 +0000
To:     Saeed Mahameed <>
Subject: Re: [PATCH net-next 00/16] mlx5 xsk updates part3 2022-09-30


This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <>:

On Fri, 30 Sep 2022 09:28:47 -0700 you wrote:
> From: Saeed Mahameed <>
> The gist of this 4 part series is in this patchset's last patch
> This series contains performance optimizations. XSK starts using the
> batching allocator, and XSK data path gets separated from the regular
> RX, allowing to drop some branches not relevant for non-XSK use cases.
> Some minor optimizations for indirect calls and need_wakeup are also
> included.
> [...]

Here is the summary with links:
  - [net-next,01/16] net/mlx5e: xsk: Use mlx5e_trigger_napi_icosq for XSK wakeup
  - [net-next,02/16] net/mlx5e: xsk: Drop the check for XSK state in mlx5e_xsk_wakeup
  - [net-next,03/16] net/mlx5e: Introduce wqe_index_mask for legacy RQ
  - [net-next,04/16] net/mlx5e: Make the wqe_index_mask calculation more exact
  - [net-next,05/16] net/mlx5e: Use partial batches in legacy RQ
  - [net-next,06/16] net/mlx5e: xsk: Use partial batches in legacy RQ with XSK
  - [net-next,07/16] net/mlx5e: Remove the outer loop when allocating legacy RQ WQEs
  - [net-next,08/16] net/mlx5e: xsk: Split out WQE allocation for legacy XSK RQ
  - [net-next,09/16] net/mlx5e: xsk: Use xsk_buff_alloc_batch on legacy RQ
  - [net-next,10/16] net/mlx5e: xsk: Use xsk_buff_alloc_batch on striding RQ
  - [net-next,11/16] net/mlx5e: Use non-XSK page allocator in SHAMPO
  - [net-next,12/16] net/mlx5e: Call mlx5e_page_release_dynamic directly where possible
  - [net-next,13/16] net/mlx5e: Optimize RQ page deallocation
  - [net-next,14/16] net/mlx5e: xsk: Support XDP metadata on XSK RQs
  - [net-next,15/16] net/mlx5e: Introduce the mlx5e_flush_rq function
  - [net-next,16/16] net/mlx5e: xsk: Use queue indices starting from 0 for XSK queues

You are awesome, thank you!
Deet-doot-dot, I am a bot.

Powered by blists - more mailing lists