From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail144.messagelabs.com (mail144.messagelabs.com [216.82.254.51]) by kanga.kvack.org (Postfix) with ESMTP id CDB7B6B016A for ; Thu, 25 Aug 2011 10:58:10 -0400 (EDT) Subject: Re: [PATCH] memcg: remove unneeded preempt_disable From: Peter Zijlstra Date: Thu, 25 Aug 2011 16:57:52 +0200 In-Reply-To: <20110818144025.8e122a67.akpm@linux-foundation.org> References: <1313650253-21794-1-git-send-email-gthelen@google.com> <20110818144025.8e122a67.akpm@linux-foundation.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Message-ID: <1314284272.27911.32.camel@twins> Mime-Version: 1.0 Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Morton Cc: Greg Thelen , linux-kernel@vger.kernel.org, linux-mm@kvack.org, KAMEZAWA Hiroyuki , Balbir Singh , Daisuke Nishimura , linux-arch@vger.kernel.org On Thu, 2011-08-18 at 14:40 -0700, Andrew Morton wrote: >=20 > I think I'll apply it, as the call frequency is low (correct?) and the > problem will correct itself as other architectures implement their > atomic this_cpu_foo() operations.=20 Which leads me to wonder, can anything but x86 implement that this_cpu_* muck? I doubt any of the risk chips can actually do all this. Maybe Itanic, but then that seems to be dying fast. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org