From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [patch] rt: res_counter fix, v2 Date: Thu, 12 Feb 2009 18:29:09 +0100 Message-ID: <1234459749.10603.35.camel@laptop> References: <20090212005032.GA4788@nowhere> <20090212021257.GB4697@nowhere> <20090212101650.GA1096@elte.hu> <20090212102113.GA10031@elte.hu> <20090212194644.98d275cf.kamezawa.hiroyu@jp.fujitsu.com> <20090212112854.GD31613@elte.hu> <20090212165833.GB6298@balbir.in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Ingo Molnar , KAMEZAWA Hiroyuki , Frederic Weisbecker , Thomas Gleixner , LKML , rt-users , Steven Rostedt , Carsten Emde , Clark Williams To: balbir@linux.vnet.ibm.com Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:55750 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750742AbZBLR32 (ORCPT ); Thu, 12 Feb 2009 12:29:28 -0500 In-Reply-To: <20090212165833.GB6298@balbir.in.ibm.com> Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Thu, 2009-02-12 at 22:28 +0530, Balbir Singh wrote: > > _nort() will just turn them into NOPs in essence. > > > > The question is, are these local IRQ flags manipulations really needed > > in this code, and if yes, why? > > We needed the local IRQ flags, since these counters are updated from > page fault context and from reclaim context with lru_lock held with > IRQ's disabled. I've been thinking about replacing the spin lock with > seq lock, but have not gotten to it yet. Ah, in that case we can get away with _nort I think, as both those contexts are preemptable on -rt.