On Thu, Jun 26, 2025 at 03:16:49AM -0700, Christoph Hellwig wrote:
> On Wed, Jun 25, 2025 at 07:08:57AM -0700, Boqun Feng wrote:
> > Sure, I will put one for the future version, here is the gist:
>
> Thanks a lot!
>
> > The updater's wait can finish immediately if no one is accessing 'a', in
> >
On 2025-06-26 06:16, Christoph Hellwig wrote:
On Wed, Jun 25, 2025 at 07:08:57AM -0700, Boqun Feng wrote:
Sure, I will put one for the future version, here is the gist:
Thanks a lot!
The updater's wait can finish immediately if no one is accessing 'a', in
other words it doesn't need to wait
On Wed, Jun 25, 2025 at 07:08:57AM -0700, Boqun Feng wrote:
> Sure, I will put one for the future version, here is the gist:
Thanks a lot!
> The updater's wait can finish immediately if no one is accessing 'a', in
> other words it doesn't need to wait for reader 2.
So basically it is the RCU con
On Wed, Jun 25, 2025 at 08:25:52AM -0400, Mathieu Desnoyers wrote:
> On 2025-06-24 23:10, Boqun Feng wrote:
> > Hi,
> >
> > This is the official first version of simple hazard pointers following
> > the RFC:
> >
> >
> > https://lore.kernel.org/lkml/20250414060055.341516-1-boqun.f...@gmail.co
On Wed, Jun 25, 2025 at 05:05:11AM -0700, Christoph Hellwig wrote:
> On Tue, Jun 24, 2025 at 08:10:53PM -0700, Boqun Feng wrote:
> > Hi,
> >
> > This is the official first version of simple hazard pointers following
> > the RFC:
>
> Can you please put an explanation of what hazard pointers are
>
On Tue, Jun 24, 2025 at 08:10:53PM -0700, Boqun Feng wrote:
> Hi,
>
> This is the official first version of simple hazard pointers following
> the RFC:
Can you please put an explanation of what hazard pointers are
prominently into this cover letter?
On 2025-06-24 23:10, Boqun Feng wrote:
Hi,
This is the official first version of simple hazard pointers following
the RFC:
https://lore.kernel.org/lkml/20250414060055.341516-1-boqun.f...@gmail.com/
I rebase it onto v6.16-rc3 and hope to get more feedback this time.
Thanks a lot for B
Hi,
This is the official first version of simple hazard pointers following
the RFC:
https://lore.kernel.org/lkml/20250414060055.341516-1-boqun.f...@gmail.com/
I rebase it onto v6.16-rc3 and hope to get more feedback this time.
Thanks a lot for Breno Leitao to try the RFC out and share
Hello, Breno!
> Hello Vlad,
>
> On Wed, Apr 16, 2025 at 05:04:31PM +0200, Uladzislau Rezki wrote:
> > On Wed, Apr 16, 2025 at 07:14:04AM -0700, Breno Leitao wrote:
> > > Hi Boqun,
> > >
> > > On Sun, Apr 13, 2025 at 11:00:47PM -0700, Boqun Feng wrote:
> > >
> > > > Overall it looks promising to
Hello Vlad,
On Wed, Apr 16, 2025 at 05:04:31PM +0200, Uladzislau Rezki wrote:
> On Wed, Apr 16, 2025 at 07:14:04AM -0700, Breno Leitao wrote:
> > Hi Boqun,
> >
> > On Sun, Apr 13, 2025 at 11:00:47PM -0700, Boqun Feng wrote:
> >
> > > Overall it looks promising to me, but I would like to see how
On Wed, Apr 16, 2025 at 07:14:04AM -0700, Breno Leitao wrote:
> Hi Boqun,
>
> On Sun, Apr 13, 2025 at 11:00:47PM -0700, Boqun Feng wrote:
>
> > Overall it looks promising to me, but I would like to see how it
> > performs in the environment of Breno. Also as Paul always reminds me:
> > buggy code
Hi Boqun,
On Sun, Apr 13, 2025 at 11:00:47PM -0700, Boqun Feng wrote:
> Overall it looks promising to me, but I would like to see how it
> performs in the environment of Breno. Also as Paul always reminds me:
> buggy code usually run faster, so please take a look in case I'm missing
> something ;
Hi,
This RFC is mostly a follow-up on discussion:
https://lore.kernel.org/lkml/20250321-lockdep-v1-1-78b732d19...@debian.org/
I found that using a hazard pointer variant can speed up the
lockdep_unregister_key(), on my system (a 96-cpu VMs), the results of:
time /usr/sbin/tc qd
13 matches
Mail list logo
