From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Fwd: Re: struct page field arrangement Date: Fri, 16 Mar 2007 12:37:44 +0000 Message-ID: References: <45FA948B.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45FA948B.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 16/3/07 11:58, "Jan Beulich" wrote: > Of course we could back out that changeset, but one of the reasons for > submitting it was to get closer to native. None of the fixes sound straightforward. :-) I'd suggest we back out the mm/Kconfig change for 3.0.5 (since that is close, and I'm not super confident that we'd get any of your proposed fixes correct first time) and then have a go at supporting split-ptlock in 3.0.6 timeframe. The situation after all is that our scalability beyond 4 VCPUs is currently almost certainly bottlenecked by conservative locking in Xen rather than by per-mm locking in Linux. So we're looking at complicating the Linux code close to a Xen release for no actual user benefit. -- Keir