From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: [RFC] should VM_BUG_ON(cond) really evaluate cond Date: Fri, 28 Oct 2011 03:19:21 +0200 Message-ID: <1319764761.23112.14.camel@edumazet-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: linux-kernel , Andi Kleen , netdev , Andrew Morton To: Linus Torvalds Return-path: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org In commit 4e60c86bd9e (gcc-4.6: mm: fix unused but set warnings) Andi forced VM_BUG_ON(cond) to evaluate cond, even if CONFIG_DEBUG_VM is not set : #ifdef CONFIG_DEBUG_VM #define VM_BUG_ON(cond) BUG_ON(cond) #else #define VM_BUG_ON(cond) do { (void)(cond); } while (0) #endif As a side effect, get_page()/put_page_testzero() are performing more bus transactions on contended cache line on some workloads (tcp on loopback for example, where a page is acting as a shared buffer) 0,05 : ffffffff815e4775: je ffffffff815e4970 0,05 : ffffffff815e477b: mov 0x1c(%r9),%eax // useless 3,32 : ffffffff815e477f: mov (%r9),%rax // useless 0,51 : ffffffff815e4782: lock incl 0x1c(%r9) 3,87 : ffffffff815e4787: mov (%r9),%rax 0,00 : ffffffff815e478a: test $0x80,%ah 0,00 : ffffffff815e478d: jne ffffffff815e49f2 Of course, we have to understand why (void) (atomic_read(&some_atomic) == 1); generates asm code... mov some_atomic,%eax Ah yes, this is because of the volatile... static inline int atomic_read(const atomic_t *v) { return (*(volatile int *)&(v)->counter); } So maybe a fix would be to introduce an atomic_read_stable() variant ? static inline int atomic_read_stable(const atomic_t *v) { return v->counter; } Thanks !