[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250111234502.1739-1-hdanton@sina.com>
Date: Sun, 12 Jan 2025 07:44:59 +0800
From: Hillf Danton <hdanton@...a.com>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: akpm@...ux-foundation.org,
peterz@...radead.org,
willy@...radead.org,
hannes@...xchg.org,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [PATCH v9 10/17] refcount: introduce __refcount_{add|inc}_not_zero_limited
On Sat, 11 Jan 2025 09:11:52 -0800 Suren Baghdasaryan <surenb@...gle.com>
> I see your point. I think it's a strong argument to use atomic
> directly instead of refcount for this locking. I'll try that and see
> how it looks. Thanks for the feedback!
>
Better not before having a clear answer to why is it sane to invent
anything like rwsem in 2025. What, the 40 bytes? Nope it is the
fair price paid for finer locking granuality.
BTW Vlastimil, the cc list is cut down because I have to walk around
the spam check on the mail agent side.
Powered by blists - more mailing lists