[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200827163755.GK1362448@hirez.programming.kicks-ass.net>
Date: Thu, 27 Aug 2020 18:37:55 +0200
From: peterz@...radead.org
To: linux-kernel@...r.kernel.org, mhiramat@...nel.org
Cc: Eddy_Wu@...ndmicro.com, x86@...nel.org, davem@...emloft.net,
rostedt@...dmis.org, naveen.n.rao@...ux.ibm.com,
anil.s.keshavamurthy@...el.com, linux-arch@...r.kernel.org,
cameron@...dycamel.com, oleg@...hat.com, will@...nel.org,
paulmck@...nel.org
Subject: Re: [RFC][PATCH 6/7] freelist: Lock less freelist
On Thu, Aug 27, 2020 at 06:12:43PM +0200, Peter Zijlstra wrote:
> +struct freelist_node {
> + atomic_t refs;
> + struct freelist_node *next;
> +};
Bah, the next patch relies on this structure to be ordered the other
way around.
Clearly writing code and listening to talks isn't ideal :-)
Powered by blists - more mailing lists