All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Carsten Schiers <carsten@schiers.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: AW: Load increase after memory upgrade?
Date: Tue, 28 Jun 2011 10:49:44 -0400	[thread overview]
Message-ID: <20110628144944.GA16290@dumpdata.com> (raw)
In-Reply-To: <H0000067000b47c4.1309204598.uhura.space.zz@MHS>

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.

<nods> 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

      reply	other threads:[~2011-06-28 14:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 11:29 AW: Load increase after memory upgrade? Carsten Schiers
2011-06-27 13:46 ` Konrad Rzeszutek Wilk
2011-06-27 15:37   ` Sander Eikelenboom
2011-06-27 20:00     ` AW: " Carsten Schiers
2011-06-27 20:20       ` Sander Eikelenboom
2011-06-27 20:44         ` AW: " Carsten Schiers
2011-06-27 20:46         ` Carsten Schiers
2011-06-28 14:57           ` Konrad Rzeszutek Wilk
2011-06-28 20:17             ` AW: " Carsten Schiers
2011-06-28 20:22             ` Carsten Schiers
2011-06-28 20:34               ` Konrad Rzeszutek Wilk
2011-06-29 21:17                 ` AW: " Carsten Schiers
2011-06-30 22:00                   ` Konrad Rzeszutek Wilk
2011-06-28 14:50       ` Konrad Rzeszutek Wilk
2011-06-28 20:34     ` AW: " Carsten Schiers
2011-06-27 19:56   ` Carsten Schiers
2011-06-28 14:49     ` Konrad Rzeszutek Wilk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110628144944.GA16290@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=carsten@schiers.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.