[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230911183025.5f808a70a62df79a3a1e349e@linux-foundation.org>
Date: Mon, 11 Sep 2023 18:30:25 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "NeilBrown" <neilb@...e.de>
Cc: "Chuck Lever III" <chuck.lever@...cle.com>,
"Chuck Lever" <cel@...nel.org>,
"Linux NFS Mailing List" <linux-nfs@...r.kernel.org>,
"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 Tue, 12 Sep 2023 09:19:59 +1000 "NeilBrown" <neilb@...e.de> wrote:
> Plain old list_heads (which the code currently uses) require a spinlock
> to be taken to insert something into the queue. As this is usually in
> bh context, it needs to be a spin_lock_bh(). My understanding is that
> the real-time developers don't much like us disabling bh. It isn't an
> enormous win switching from a list_head list to a llist_node list, but
> there are small gains such as object size reduction and less locking. I
> particularly wanted an easy-to-use library facility that could be
> plugged in to two different uses cases in the sunrpc code and there
> didn't seem to be one. I could have written one using list_head, but
> llist seemed a better fix. I think the code in sunrpc that uses this
> lwq looks a lot neater after the conversion.
Thanks. Could we please get words such as these into the changelog,
describing why it was felt necessary to add more library code?
And also into the .c file, to help people who are looking at it and
wondering "can I use this". And to help reviewers who are wondering
"could they have used Neil's thing".
Powered by blists - more mailing lists