From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 08/16] xenpaging: reduce MINIMUM_RESTART_TIME
Date: Wed, 3 Nov 2010 15:13:48 +0100 [thread overview]
Message-ID: <20101103141348.GB10432@aepfle.de> (raw)
In-Reply-To: <19665.22758.814027.988061@mariner.uk.xensource.com>
On Wed, Nov 03, Ian Jackson wrote:
> Olaf Hering writes ("[Xen-devel] [PATCH 08/16] xenpaging: reduce MINIMUM_RESTART_TIME"):
> > Allow runlevel 6 as default runlevel.
> ...
> > -MINIMUM_RESTART_TIME = 60
> > +MINIMUM_RESTART_TIME = 5
>
> I don't understand what this change is doing in your xenpaging series;
> nor does setting runlevel 6 as the default runlevel seem very
> sensible other than perhaps for some kind of stress testing.
>
> Perhaps this patch snuck into the series by mistake ?
Its there intentional in my series, just to get the startup code tested
automatically. The runtime code seems to work ok now that the granttable
part got fixed.
Last time I tried to get this variable into the vm config file, it did
not work as expected. Appearently its a global variable, not per guest.
And its value was changed from 20 (I think) to 60 without a good
changelog entry, not too long ago. For my testing, even 20 would have
been to long. If I use 'reboot' quickly in grub, guest runtime is around
7 seconds I think.
Too bad, this variable is only a bandaid because it doesnt know any
context of the guest. And it cant know any context. When is a guest in a
good or bad state? Should it panic, or crash? Its not easy to detect
a bad condition.
A better change would be to allow an override in the guest config file.
Olaf
next prev parent reply other threads:[~2010-11-03 14:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 22:30 [PATCH 00/16] xenpaging changes for xen-unstable Olaf Hering
2010-11-02 22:30 ` [PATCH 01/16] xenpaging: whitespace fixes after addition of __get_paged_frame Olaf Hering
2010-11-03 12:37 ` Ian Jackson
2010-11-02 22:30 ` [PATCH 02/16] xenpaging: break endless loop during inital page-out with large pagefiles Olaf Hering
2010-11-02 22:30 ` [PATCH 03/16] xenpaging: Open paging file only if xenpaging_init() succeeds Olaf Hering
2010-11-02 22:30 ` [PATCH 04/16] xenpaging: allow only one xenpaging binary per guest Olaf Hering
2010-11-02 22:30 ` [PATCH 05/16] xenpaging: update machine_to_phys_mapping during page-in and page-out Olaf Hering
2010-11-03 18:32 ` Olaf Hering
2010-11-02 22:30 ` [PATCH 06/16] xenpaging: drop paged pages in guest_remove_page Olaf Hering
2010-11-03 18:33 ` Olaf Hering
2010-11-02 22:30 ` [PATCH 07/16] xenpaging: populate only paged-out pages Olaf Hering
2010-11-03 12:38 ` Ian Jackson
2010-11-09 10:40 ` Olaf Hering
2010-11-10 8:37 ` Olaf Hering
2010-11-02 22:30 ` [PATCH 08/16] xenpaging: reduce MINIMUM_RESTART_TIME Olaf Hering
2010-11-03 12:43 ` Ian Jackson
2010-11-03 14:13 ` Olaf Hering [this message]
2010-11-03 16:55 ` Ian Jackson
2010-11-03 17:09 ` Xavier Beaudouin
2010-11-04 17:10 ` Ian Jackson
2010-11-02 22:30 ` [PATCH 09/16] xenpaging: start xenpaging via config option Olaf Hering
2010-11-02 22:30 ` [PATCH 10/16] xenpaging: add signal handling Olaf Hering
2010-11-02 22:30 ` [PATCH 11/16] xenpaging: increase recently used pages from 4MB to 64MB Olaf Hering
2010-11-02 22:30 ` [PATCH 12/16] xenpaging: print info when free request slots drop below 3 Olaf Hering
2010-11-02 22:30 ` [PATCH 13/16] xenpaging: prevent page-out of first 16MB Olaf Hering
2010-11-02 22:30 ` [PATCH 14/16] xenpaging: add dynamic startup delay for xenpaging Olaf Hering
2010-11-02 22:30 ` [PATCH 15/16] xenpaging: print p2mt for already paged-in pages Olaf Hering
2010-11-02 22:30 ` [PATCH 16/16] xenpaging: (sparse) documenation Olaf Hering
2010-11-03 8:22 ` [PATCH 00/16] xenpaging changes for xen-unstable Olaf Hering
2010-11-03 19:24 ` [PATCH 17/16] xenpaging: notify policy only on resume Olaf Hering
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=20101103141348.GB10432@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Jackson@eu.citrix.com \
--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.