From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: AW: Load increase after memory upgrade? Date: Tue, 28 Jun 2011 10:49:44 -0400 Message-ID: <20110628144944.GA16290@dumpdata.com> References: <20110627134643.GD6978@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Carsten Schiers Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Mon, Jun 27, 2011 at 09:56:38PM +0200, Carsten Schiers wrote: > >Um, so 2.6.34 to 2.6.32 causes this spike in usage? > > Definitely yes. What happens if you remove the extra 4GB of memory? You mentioned you did two things: a) more memory and b) change kernel versions. Need to narrow down which one is at fault here. > > > What is the SWIOTLB (PCI-DMA32) usage between these two kernels > > I don't understand. What do you mean? The only difference is that I call > up the swiotlb differently: > > On pvops: iommu=soft so 64MB here > On rebased: swiotlb=32,force 32MB here. Which is OK. I was somehow thinking you might have a small amount of memory in the pvops case - but you actually have a pretty big buffer there. > > BTW: changing to 64,force doesn't make a difference. So DMA might not be an issue here.. > > I attached a normal boot log of both kernels. > > > and are the drivers (budget_...) the same version? > > No, but a quick diff between the two source trees offer only minor > changes that from the first look > do not seem to be related to DMA or whatever. > > Carsten. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel