From: George Dunlap <george.dunlap@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: george.dunlap@eu.citrix.com
Subject: [PATCH 0 of 2 RFC] Rework populate-on-demand sweeping
Date: Fri, 8 Jun 2012 11:45:31 +0000 [thread overview]
Message-ID: <patchbomb.1339155931@exile> (raw)
Rework populate-on-demand sweeping
Last summer I did some work on testing whether our PoD sweeping code
was achieving its goals: namely, never crashing unnecessairly,
minimizing boot time, and maximizing the number of superpages in the
p2m table.
This is one of the resulting patch series.
I'm posting it to make sure that maintainers think it's still suitable
for inclusion in 4.2. The patces against 4.1 have been extensively in
the XenServer testing framework and have been in use by XenServer
customers for over 9 months now. But the p2m code has changed
extensively in that time, so one could argue that the testing doesn't
give us the same degree of confidence in the patches against 4.2 as
against 4.1. (On the other hand, the PoD code hasn't changed that
much.)
I haven't done more than compile-test it at this point, so please just
review ideas and "is this 4.2 material". If I get positive feedback,
I'll do more testing and re-submit.
next reply other threads:[~2012-06-08 11:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 11:45 George Dunlap [this message]
2012-06-08 11:45 ` [PATCH 1 of 2 RFC] xen, pod: Zero-check recently populated pages (checklast) George Dunlap
2012-06-08 12:02 ` Jan Beulich
2012-06-14 9:07 ` Tim Deegan
2012-06-14 14:24 ` George Dunlap
2012-06-14 15:36 ` Tim Deegan
2012-06-08 11:45 ` [PATCH 2 of 2 RFC] xen, pod: Only sweep in an emergency, and only for 4k pages George Dunlap
2012-06-14 9:11 ` Tim Deegan
2012-06-14 12:42 ` George Dunlap
2012-06-14 13:13 ` Tim Deegan
2012-06-14 13:32 ` George Dunlap
2012-06-14 9:12 ` [PATCH 0 of 2 RFC] Rework populate-on-demand sweeping Tim Deegan
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=patchbomb.1339155931@exile \
--to=george.dunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).