All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Graham, Simon" <Simon.Graham@stratus.com>
To: Iustin Pop <iusty@k1024.org>
Cc: xen-devel@lists.xensource.com
Subject: RE: Reducing impact of save/restore/dump on Dom0
Date: Tue, 6 Feb 2007 12:46:52 -0500	[thread overview]
Message-ID: <342BAC0A5467384983B586A6B0B3767104A69C19@EXNA.corp.stratus.com> (raw)

> On linux, there is another way beside O_DIRECT: it's possible to
reduce
> the memory used for cached writing using the sysctl vm.dirty_ratio;
> I've
> used this to reduce the impact of heavy cached writes on dom0 with
good
> results.
> 
> Maybe it helps for save/dump also...

Oh interesting -- I shall look into this. 

I just took a quick peek and it is set to 40% in Dom0; I do see free
memory go to zero during a dump (and save/restore) plus I see the
waitIO% go to near 100% and Dom0 becomes somewhat unresponsive;
specifically what we see is that domain boot fails during this time
because of a XenBus timeout waiting for the hotplug scripts to finish
adding the VBD in Dom0.

I still feel that dump/save/restore files really don't belong in the
system cache at all since they just pollute the cache for no ggood
reason.

Thanks,
Simon

         reply	other threads:[~2007-02-06 17:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06 15:43 Reducing impact of save/restore/dump on Dom0 Graham, Simon
2007-02-06 16:23 ` John Levon
2007-02-06 17:36 ` Iustin Pop
2007-02-06 17:46   ` Graham, Simon [this message]
2007-02-06 18:35     ` Iustin Pop
2007-02-06 23:00 ` Ian Pratt
2007-02-06 23:20   ` Jeremy Fitzhardinge
2007-02-07  6:40     ` Rusty Russell
2007-02-07  7:41       ` Jeremy Fitzhardinge
2007-02-07 12:11 ` Andi Kleen
2007-02-07 12:52   ` Ian Pratt
2007-02-07 12:58     ` Andi Kleen
2007-02-06 17:25 Graham, Simon
2007-02-06 19:21 Graham, Simon
2007-02-07 12:56 Graham, Simon

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=342BAC0A5467384983B586A6B0B3767104A69C19@EXNA.corp.stratus.com \
    --to=simon.graham@stratus.com \
    --cc=iusty@k1024.org \
    --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.