From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Christoph Lameter <cl@linux.com>
Cc: akpm@linux-foundation.org, Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Eric Dumazet <eric.dumazet@gmail.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [thiscpuops upgrade 10/10] Lockless (and preemptless) fastpaths for slub
Date: Tue, 23 Nov 2010 20:02:53 -0500 [thread overview]
Message-ID: <20101124010252.GB8264@Krystal> (raw)
In-Reply-To: <20101123235201.758191189@linux.com>
* Christoph Lameter (cl@linux.com) wrote:
[...]
> @@ -1737,23 +1770,53 @@ static __always_inline void *slab_alloc(
> {
> void **object;
> struct kmem_cache_cpu *c;
> - unsigned long flags;
> + unsigned long tid;
>
> if (slab_pre_alloc_hook(s, gfpflags))
> return NULL;
>
> - local_irq_save(flags);
> +redo:
> + /*
> + * Must read kmem_cache cpu data via this cpu ptr. Preemption is
> + * enabled. We may switch back and forth between cpus while
> + * reading from one cpu area. That does not matter as long
> + * as we end up on the original cpu again when doing the cmpxchg.
> + */
> c = __this_cpu_ptr(s->cpu_slab);
> +
> + /*
> + * The transaction ids are globally unique per cpu and per operation on
> + * a per cpu queue. Thus they can be guarantee that the cmpxchg_double
> + * occurs on the right processor and that there was no operation on the
> + * linked list in between.
> + */
There seems to be some voodoo magic I don't understand here. I'm curious to see
what happens if we have:
CPU A CPU B
slab_alloc()
c = __this_cpu_ptr(s->cpu_slab);
tid = c->tid
thread migrated to CPU B
slab_alloc()
c = __this_cpu_ptr(s->cpu_slab);
tid = c->tid
... ...
irqsafe_cmpxchg_double
- expect tid, on CPU A, success
migrate back to CPU A
irqsafe_cmpxchg_double
- expect (same) tid, on CPU A, success
So either there is a crucially important point I am missing, or the transaction
ID does not seem to be truly unique due to migration.
Thanks,
Mathieu
> + tid = c->tid;
> + barrier();
> +
> object = c->freelist;
> - if (unlikely(!object || !node_match(c, node)))
> + if (unlikely(!object || !node_match(c, c->node)))
>
> - object = __slab_alloc(s, gfpflags, node, addr, c);
> + object = __slab_alloc(s, gfpflags, c->node, addr);
>
> else {
> - c->freelist = get_freepointer(s, object);
> + /*
> + * The cmpxchg will only match if there was not additonal
> + * operation and if we are on the right processor.
> + */
> + if (unlikely(!irqsafe_cmpxchg_double(&s->cpu_slab->freelist, object, tid,
> + get_freepointer(s, object), next_tid(tid)))) {
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-11-24 1:02 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 23:51 [thiscpuops upgrade 00/10] Upgrade of this_cpu_ops Christoph Lameter
2010-11-23 23:51 ` [thiscpuops upgrade 01/10] percpucounter: Optimize __percpu_counter_add a bit through the use of this_cpu() options Christoph Lameter
2010-11-24 7:07 ` Pekka Enberg
2010-11-26 15:43 ` Tejun Heo
2010-11-23 23:51 ` [thiscpuops upgrade 02/10] vmstat: Optimize zone counter modifications through the use of this cpu operations Christoph Lameter
2010-11-26 16:25 ` Tejun Heo
2010-11-23 23:51 ` [thiscpuops upgrade 03/10] percpu: Generic support for this_cpu_add,sub,dec,inc_return Christoph Lameter
2010-11-26 16:31 ` Tejun Heo
2010-11-26 16:37 ` Christoph Lameter
2010-11-26 16:39 ` Tejun Heo
2010-11-23 23:51 ` [thiscpuops upgrade 04/10] x86: Support " Christoph Lameter
2010-11-26 16:33 ` Tejun Heo
2010-11-23 23:51 ` [thiscpuops upgrade 05/10] x86: Use this_cpu_inc_return for nmi counter Christoph Lameter
2010-11-26 16:35 ` Tejun Heo
2010-11-26 17:02 ` Christoph Lameter
2010-11-26 17:05 ` Tejun Heo
2010-11-23 23:51 ` [thiscpuops upgrade 06/10] vmstat: Use this_cpu_inc_return for vm statistics Christoph Lameter
2010-11-23 23:51 ` [thiscpuops upgrade 07/10] highmem: Use this_cpu_xx_return() operations Christoph Lameter
2010-11-23 23:51 ` [thiscpuops upgrade 08/10] percpu: generic this_cpu_cmpxchg() and this_cpu_cmpxchg_double support Christoph Lameter
2010-11-26 16:51 ` Tejun Heo
2010-11-26 16:56 ` Eric Dumazet
2010-11-26 16:58 ` Tejun Heo
2010-11-26 17:01 ` Eric Dumazet
2010-11-26 17:07 ` Tejun Heo
2010-11-26 17:16 ` Eric Dumazet
2010-11-23 23:51 ` [thiscpuops upgrade 09/10] x86: this_cpu_cmpxchg and this_cpu_cmpxchg_double operations Christoph Lameter
2010-11-24 0:41 ` Eric Dumazet
2010-11-24 3:11 ` Christoph Lameter
2010-11-24 7:05 ` Pekka Enberg
2010-11-24 0:44 ` Mathieu Desnoyers
2010-11-23 23:51 ` [thiscpuops upgrade 10/10] Lockless (and preemptless) fastpaths for slub Christoph Lameter
2010-11-24 0:22 ` Eric Dumazet
2010-11-24 3:13 ` Christoph Lameter
2010-11-24 4:37 ` Christoph Lameter
2010-11-24 1:02 ` Mathieu Desnoyers [this message]
2010-11-24 1:05 ` Mathieu Desnoyers
2010-11-24 3:09 ` Christoph Lameter
2010-11-24 7:16 ` Pekka Enberg
2010-11-24 16:17 ` Christoph Lameter
2010-11-24 16:37 ` Pekka Enberg
2010-11-24 16:45 ` Christoph Lameter
2010-11-24 16:47 ` Pekka Enberg
2010-11-24 16:55 ` Christoph Lameter
2010-11-24 19:37 ` Jeremy Fitzhardinge
2010-11-24 19:53 ` Christoph Lameter
2010-11-24 20:01 ` Jeremy Fitzhardinge
2010-11-24 19:56 ` Mathieu Desnoyers
2010-11-24 8:15 ` Peter Zijlstra
2010-11-24 16:14 ` Christoph Lameter
2010-11-24 17:26 ` Peter Zijlstra
2010-11-24 18:08 ` Christoph Lameter
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=20101124010252.GB8264@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=tj@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