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]
Message-Id: 
 <169744382398.7812.17747534311837223482.git-patchwork-notify@kernel.org>
Date: Mon, 16 Oct 2023 08:10:23 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Christian Marangi <ansuelsmth@...il.com>
Cc: rajur@...lsio.com, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [net-next PATCH] net: cxgb3: simplify logic for rspq_check_napi

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:

On Thu, 12 Oct 2023 11:14:29 +0200 you wrote:
> Simplify logic for rspq_check_napi.
> Drop redundant and wrong napi_is_scheduled call as it's not race free
> and directly use the output of napi_schedule to understand if a napi is
> pending or not.
> 
> rspq_check_napi main logic is to check if is_new_response is true and
> check if a napi is not scheduled. The result of this function is then
> used to detect if we are missing some interrupt and act on top of
> this... With this knowing, we can rework and simplify the logic and make
> it less problematic with testing an internal bit for napi.
> 
> [...]

Here is the summary with links:
  - [net-next] net: cxgb3: simplify logic for rspq_check_napi
    https://git.kernel.org/netdev/net-next/c/101c6032031f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ