netdev - Re: [PATCH net-next 00/13] bnxt

lists.openwall.net		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 linux-cve-announce 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: Sun, 29 Oct 2023 23:33:08 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Michael Chan <michael.chan@...adcom.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, gospo@...adcom.com
Subject: Re: [PATCH net-next 00/13] bnxt_en: TX path improvements

On Fri, 27 Oct 2023 16:22:39 -0700 Michael Chan wrote:
> All patches in this patchset are related to improving the TX path.
> There are 2 areas of improvements:
> 
> 1. The TX interrupt logic currently counts the number of TX completions
> to determine the number of TX SKBs to free.  We now change it so that
> the TX completion will now contain the hardware consumer index
> information.  The driver will keep track of the latest hardware
> consumer index from the last TX completion and clean up all TX SKBs
> up to that index.  This scheme aligns better with future chips and
> allows xmit_more code path to be more optimized.
> 
> 2. The current driver logic requires an additional MSIX for each
> additional MQPRIO TX ring.  This scheme uses too many MSIX vectors if
> the user enables a large number of MQPRIO TCs.  We now use a new scheme
> that will use the same MSIX for all the MQPRIO TX rings for each
> ethtool channel.  Each ethtool TX channel can have up to 8 MQPRIO
> TX rings and now they all will share the same MSIX.

## Form letter - net-next-closed

The merge window for v6.7 has begun and we have already posted our pull
request. Therefore net-next is closed for new drivers, features, code
refactoring and optimizations. We are currently accepting bug fixes only.

Please repost when net-next reopens after Nov 12th.

RFC patches sent for review only are obviously welcome at any time.

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
-- 
pw-bot: defer