mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: paulmck@kernel.org
Cc: Boqun Feng <boqun.feng@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v5 1/2] hazptr: Implement Hazard Pointers
Date: Thu, 9 Jul 2026 12:03:49 -0400	[thread overview]
Message-ID: <20829c0a-a8f6-48f2-b63f-b1f277d4afa1@efficios.com> (raw)
In-Reply-To: <9a33fa22-cc1e-4dcf-bb7b-667a859d2c53@paulmck-laptop>

On 2026-07-09 12:02, Paul E. McKenney wrote:
[...]
> Am I perhaps just overflowing the backup slots?  Or is there some sort
> of memory allocation behind the scenes that I am missing?

I found the root cause, fix coming shortly.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com

  reply	other threads:[~2026-07-09 16:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 20:44 [RFC PATCH v5 0/2] " Mathieu Desnoyers
2026-02-23 20:44 ` [RFC PATCH v5 1/2] hazptr: Implement " Mathieu Desnoyers
2026-06-26 23:06   ` Paul E. McKenney
2026-06-27  3:56     ` Mathieu Desnoyers
2026-06-27  4:14       ` Paul E. McKenney
2026-06-27 12:56         ` Mathieu Desnoyers
2026-06-27 15:21           ` Mathieu Desnoyers
2026-06-27 17:36             ` Paul E. McKenney
2026-07-07 19:40               ` Mathieu Desnoyers
2026-07-07 21:42                 ` Paul E. McKenney
2026-07-08 22:55                   ` Paul E. McKenney
2026-07-09  2:45                     ` Mathieu Desnoyers
2026-07-09  3:28                       ` Paul E. McKenney
2026-07-09 16:02                         ` Paul E. McKenney
2026-07-09 16:03                           ` Mathieu Desnoyers [this message]
2026-07-09 16:06                             ` Paul E. McKenney
2026-02-23 20:44 ` [RFC PATCH v5 2/2] hazptr: Add refscale test Mathieu Desnoyers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20829c0a-a8f6-48f2-b63f-b1f277d4afa1@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®