netdev - Re: [Intel-wired-lan] [PATCH RFC net-next 2/2] idpf: use napi's irq affinity

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <fd139f17-6c19-470b-ba28-fead978cb674@intel.com>
Date: Fri, 6 Dec 2024 10:58:19 -0700
From: Ahmed Zaki <ahmed.zaki@...el.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>
CC: <intel-wired-lan@...ts.osuosl.org>, <netdev@...r.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH RFC net-next 2/2] idpf: use napi's irq
 affinity

On 2024-12-06 1:29 a.m., Paul Menzel wrote:
> Dear Ahmed,
> 
> 
> Thank you for your patch.
> 
> Am 06.12.24 um 01:12 schrieb Ahmed Zaki:
>> Delete the driver CPU affinity info and use the core's napi config
>> instead.
> 
> Excuse my ignorance, but could you please state why? (Is the core’s napi 
> config the successor?)
> 

Hi Paul

I am not sure I understand what you mean by "successor"!

This patch is an example on how the new "napi_config->affinity_mask" 
defined in patch 1/2 of the series could be used instead of keeping the 
affinity mask in the driver.

It is kind of code cleanup since the task can be done in the core for 
all drivers.