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: <4D5C2693-40E9-467D-9F2F-59D92CBE9D3B@oracle.com>
Date:   Mon, 11 Sep 2023 20:30:40 +0000
From:   Chuck Lever III <chuck.lever@...cle.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
CC:     Chuck Lever <cel@...nel.org>,
        Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
        Neil Brown <neilb@...e.de>,
        Liam Howlett <liam.howlett@...cle.com>,
        Kees Cook <keescook@...omium.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        David Gow <davidgow@...gle.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 11/17] lib: add light-weight queuing mechanism.



> On Sep 11, 2023, at 2:13 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> On Mon, 11 Sep 2023 10:39:43 -0400 Chuck Lever <cel@...nel.org> wrote:
> 
>> lwq is a FIFO single-linked queue that only requires a spinlock
>> for dequeueing, which happens in process context.  Enqueueing is atomic
>> with no spinlock and can happen in any context.
> 
> What is the advantage of this over using one of the library
> facilities which we already have?

I'll let the patch author respond to that question, but let me pose
one of my own: What pre-existing facilities are you thinking of, so
that I may have a look?


--
Chuck Lever


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ