[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57C9024A16AD2D4C97DC78E552063EA3E32264A8@orsmsx505.amr.corp.intel.com>
Date: Wed, 14 Oct 2009 09:42:31 -0700
From: "Luck, Tony" <tony.luck@...el.com>
To: Christoph Lameter <cl@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
"mingo@...hat.com" <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"hpa@...or.com" <hpa@...or.com>,
"cebbert@...hat.com" <cebbert@...hat.com>
Subject: RE: [PATCH 13/16] percpu: remove per_cpu__ prefix.
>> -#define __ia64_per_cpu_var(var) per_cpu__##var
>> +#define __ia64_per_cpu_var(var) var
>
> IA64 could completely drop the macro? Tony?
A #define that just returns its original argument untouched
does seem to be a no-op. So I suppose we could just fix
the dozen or so places where it is used to just use the
variable directly.
But that would leave no visual indicator in the source
code that a per-cpu variable was being used. E.g. in
delayed_tlb_flush() we'd end up with:
if (unlikely(ia64_need_tlb_flush)) {
spin_lock ...
if (ia64_need_tlb_flush) {
local_flush_tlb_all();
ia64_need_tlb_flush = 0;
}
spin_unlock ...
}
This might cause confusion to anyone who is looking at
this code and has let the
DECLARE_PER_CPU(u8, ia64_need_tlb_flush);
scroll off the top of their screen. I'd be tempted to go
and change all the names to make this obvious:
DECLARE_PER_CPU(u8, PERCPU_ia64_need_tlb_flush);
-Tony
--
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