From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752895Ab1HYO6Q (ORCPT ); Thu, 25 Aug 2011 10:58:16 -0400 Received: from merlin.infradead.org ([205.233.59.134]:46940 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751612Ab1HYO6O convert rfc822-to-8bit (ORCPT ); Thu, 25 Aug 2011 10:58:14 -0400 Subject: Re: [PATCH] memcg: remove unneeded preempt_disable From: Peter Zijlstra 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 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: 8BIT X-Mailer: Evolution 3.0.2- Message-ID: <1314284272.27911.32.camel@twins> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2011-08-18 at 14:40 -0700, Andrew Morton wrote: > > 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. 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.