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]
Date:   Wed, 25 Oct 2023 14:17:32 -0400
From:   Daniel Jordan <daniel.m.jordan@...cle.com>
To:     Wang Jinchao <wangjinchao@...sion.com>
Cc:     Steffen Klassert <steffen.klassert@...unet.com>,
        linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
        stone.xulei@...sion.com
Subject: Re: [RFC v2] padata: Simplify sysfs cpumask and sequencing logic

Hello,

On Thu, Oct 12, 2023 at 10:06:40AM +0800, Wang Jinchao wrote:
> Utilizing the WQ_SYSFS from workqueue to support sysfs
> ======================================================
>
> Padata relies on workqueue, and since workqueue has already implemented
> support for cpumask through WQ_SYSFS, we can reuse this functionality
> and avoid redundant implementation.
> Link: https://docs.kernel.org/core-api/workqueue.html#affinity-scopes

Keeping the existing padata sysfs paths seems best, as mentioned in the
other thread.  

> Using completion to ensure the sequencing of the 'serial()'
> ===========================================================

I responded in the other RFC thread.


Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ