From: peterz@infradead.org
To: Cameron <cameron@moodycamel.com>
Cc: linux-kernel@vger.kernel.org, mhiramat@kernel.org,
Eddy_Wu@trendmicro.com, x86@kernel.org, davem@davemloft.net,
rostedt@goodmis.org, naveen.n.rao@linux.ibm.com,
anil.s.keshavamurthy@intel.com, linux-arch@vger.kernel.org,
oleg@redhat.com, will@kernel.org, paulmck@kernel.org
Subject: Re: [RFC][PATCH 6/7] freelist: Lock less freelist
Date: Thu, 27 Aug 2020 18:56:05 +0200 [thread overview]
Message-ID: <20200827165605.GL1362448@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFCw3doX6KK5DwpG_OB331Mdw8uYeVqn8YPTjKh_a-m7ZB9+3A@mail.gmail.com>
On Thu, Aug 27, 2020 at 12:49:20PM -0400, Cameron wrote:
> For what it's worth, the freelist.h code seems to be a faithful adaptation
> of my original blog post code. Didn't think it would end up in the Linux
> kernel one day :-)
Hehe, I ran into the traditional ABA problem for the lockless stack and
asked google, your blog came up.
I'll try and actually think about it a little when the current (virtual)
conference is over.
Are you Ok with the License I put on it, GPLv2 or BDS-2 ?
> I'm just wondering if the assumption that "nodes are never freed until
> after the free list is destroyed" will hold true in the intended use case?
It does, the nodes are only deleted once the whole freelist object is
discarded.
next prev parent reply other threads:[~2020-08-27 16:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 16:12 [RFC][PATCH 0/7] kprobes: Make kretprobes lockless Peter Zijlstra
2020-08-27 16:12 ` [RFC][PATCH 1/7] llist: Add nonatomic __llist_add() Peter Zijlstra
2020-08-27 16:12 ` [RFC][PATCH 2/7] sched: Fix try_invoke_on_locked_down_task() semantics Peter Zijlstra
2020-08-27 16:12 ` [RFC][PATCH 3/7] kprobes: Remove kretprobe hash Peter Zijlstra
2020-08-27 18:00 ` Masami Hiramatsu
2020-08-28 8:44 ` peterz
2020-08-28 9:07 ` Masami Hiramatsu
2020-08-28 4:44 ` Masami Hiramatsu
2020-08-28 13:11 ` Eddy_Wu
2020-08-28 13:38 ` peterz
2020-08-28 13:51 ` Masami Hiramatsu
2020-08-28 13:58 ` peterz
2020-08-28 14:19 ` Masami Hiramatsu
2020-08-28 14:11 ` Eddy_Wu
2020-08-28 14:19 ` peterz
2020-08-28 14:41 ` Masami Hiramatsu
2020-08-28 14:49 ` Masami Hiramatsu
2020-08-27 16:12 ` [RFC][PATCH 4/7] kprobe: Dont kfree() from breakpoint context Peter Zijlstra
2020-08-27 16:12 ` [RFC][PATCH 5/7] asm-generic/atomic: Add try_cmpxchg() fallbacks Peter Zijlstra
2020-08-27 16:12 ` [RFC][PATCH 6/7] freelist: Lock less freelist Peter Zijlstra
2020-08-27 16:37 ` peterz
[not found] ` <CAFCw3doX6KK5DwpG_OB331Mdw8uYeVqn8YPTjKh_a-m7ZB9+3A@mail.gmail.com>
2020-08-27 16:56 ` peterz [this message]
2020-08-27 17:00 ` Cameron
2020-08-27 19:08 ` Boqun Feng
2020-08-27 19:57 ` Cameron
2020-08-28 1:34 ` Boqun Feng
2020-08-28 4:03 ` Lai Jiangshan
2020-08-28 14:46 ` Oleg Nesterov
2020-08-28 15:29 ` peterz
2020-08-29 3:05 ` Cameron
2020-08-27 16:12 ` [RFC][PATCH 7/7] kprobes: Replace rp->free_instance with freelist Peter Zijlstra
2020-08-28 8:48 ` peterz
2020-08-28 9:13 ` Masami Hiramatsu
2020-08-28 9:18 ` peterz
2020-08-28 10:44 ` Masami Hiramatsu
2020-08-29 2:29 ` Cameron
2020-08-29 2:31 ` Cameron
2020-08-29 9:15 ` Masami Hiramatsu
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=20200827165605.GL1362448@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Eddy_Wu@trendmicro.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=cameron@moodycamel.com \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=will@kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).