From: Ralf Baechle Date: Thu, 7 Dec 2006 08:11:33 +0000 (-0800) Subject: [NET]: Memory barrier cleanups X-Git-Tag: v2.6.20-rc1~145^2^2~7^2~10 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e16aa207ccb61c5111525c462eeeba1f3f5fd370;p=pandora-kernel.git [NET]: Memory barrier cleanups I believe all the below memory barriers only matter on SMP so therefore the smp_* variant of the barrier should be used. I'm wondering if the barrier in net/ipv4/inet_timewait_sock.c should be dropped entirely. schedule_work's implementation currently implies a memory barrier and I think sane semantics of schedule_work() should imply a memory barrier, as needed so the caller shouldn't have to worry. It's not quite obvious why the barrier in net/packet/af_packet.c is needed; maybe it should be implied through flush_dcache_page? Signed-off-by: Ralf Baechle Signed-off-by: David S. Miller --- Reading git-diff-tree failed