[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150106114842.GP10476@twins.programming.kicks-ass.net>
Date: Tue, 6 Jan 2015 12:48:42 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Kent Overstreet <kmo@...erainc.com>
Cc: Sedat Dilek <sedat.dilek@...il.com>,
Dave Jones <davej@...emonkey.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, Chris Mason <clm@...com>
Subject: Re: Linux 3.19-rc3
Looking at that closure stuff, why is there an smp_mb() in
closure_wake_up() ? Typically wakeup only needs to imply a wmb.
Also note that __closure_wake_up() starts with a fully serializing
instruction (xchg) and thereby already implies the full barrier.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists