From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753670Ab0CMBxR (ORCPT ); Fri, 12 Mar 2010 20:53:17 -0500 Received: from www.tglx.de ([62.245.132.106]:42511 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751367Ab0CMBxQ (ORCPT ); Fri, 12 Mar 2010 20:53:16 -0500 Date: Sat, 13 Mar 2010 02:52:45 +0100 (CET) From: Thomas Gleixner To: Suresh Siddha cc: Robin Holt , Ingo Molnar , "H. Peter Anvin" , "Pallipadi, Venkatesh" , Linux Kernel Mailing List , "x86@kernel.org" Subject: Re: [Patch] x86,pat Update the page flags for memtype atomically instead of using memtype_lock. In-Reply-To: <1268444762.2793.197.camel@sbs-t61.sc.intel.com> Message-ID: References: <20100311161700.GC5685@sgi.com> <1268439313.2793.148.camel@sbs-t61.sc.intel.com> <1268444762.2793.197.camel@sbs-t61.sc.intel.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 12 Mar 2010, Suresh Siddha wrote: > On Fri, 2010-03-12 at 17:08 -0800, Thomas Gleixner wrote: > > On Fri, 12 Mar 2010, Suresh Siddha wrote: > > > On Thu, 2010-03-11 at 08:17 -0800, Robin Holt wrote: > > > > Changes since -V1: > > > > 1) Introduce atomically setting and clearing the page flags and not > > > > using the global memtype_lock to protect page->flags. > > > > > > > > 2) This allowed me the opportunity to convert the rwlock back into a > > > > spinlock and not affect _MY_ tests performance as all the pages my test > > > > was utilizing are tracked by struct pages. > > > > > > Can you also include this spinlock to rwlock conversion, which can be > > > used for non RAM pages as a second patch? > > > > spinlock -> rwlock conversion ? I hope you meant it the other way > > round as Robin said in #2 :) > > Thomas, No. I meant converting the existing memtype_lock which is a > spinlock into rwlock. Robin has this in the first version of the patch > but he dropped it in a later version as he avoided this lock for RAM > pages. > > Just wanted to make sure that we address the perf aspect even for non > RAM pages by converting the memtype_lock into rwlock before some one > else reports a similar issue for non RAM pages. Care to explain why a rwlock is a good solution and which problem is solved by the conversion of a spinlock to a rwlock ? Thanks, tglx