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: linux <linux@eikelenboom.it>, xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: AW: Re: AW: Load increase after memory upgrade?
Date: Tue, 28 Jun 2011 10:57:21 -0400	[thread overview]
Message-ID: <20110628145721.GC16290@dumpdata.com> (raw)
In-Reply-To: <H0000067000b47f5.1309207574.uhura.space.zz@MHS>

On Mon, Jun 27, 2011 at 10:46:15PM +0200, Carsten Schiers wrote:
> >I'm running konrad's master 
> tree(git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git) with 
> a additional patch that's the last one in his "devel/xen-pciback-0.6.1" 
> tree >(xen/pciback: revert the name of the PCI driver to ...).
> >The patch is necessary, otherwise the xen toolstack doesn't see the 
> devices being owned by pciback.
> 
> Forget what I just mailed. It's a head. I am not very used to all these 
> git thingies...
> 
> Is there an easy way to describe the steps to do after
> 
>   git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git


Um, well, lets take one thing at a time.

a). What is the version of Dom0? Are you swapping that out? If so, and you
want the latests then the next step is to do:

cd xen
git merge origin/devel/xen-pciback-0.6.1
make

b). If you just want to use the later version of a kernel for DomU, you don't
need the xen pciback. You need the xen pcifront - which has some bug-fixes in 2.6.39.
So you can:

cd xen
git checkout v2.6.39
make

c). If you want to see if the fault here lies in the bounce buffer being used more
often in the DomU b/c you have 8GB of memory now and you end up using more pages
past 4GB (in DomU), I can cook up a patch to figure this out. But an easier way is
to just do (on the Xen hypervisor line): mem=4G and that will make think you only have
4GB of physical RAM.  If the load comes back to the normal "amount" then the likely
culprit is that and we can think on how to fix this.

  reply	other threads:[~2011-06-28 14:57 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 [this message]
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

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=20110628145721.GC16290@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=carsten@schiers.de \
    --cc=linux@eikelenboom.it \
    --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.