From: Tim Deegan <Tim.Deegan@citrix.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1 of 4] p2m: Keep statistics on order of p2m entries
Date: Mon, 9 May 2011 09:27:16 +0100 [thread overview]
Message-ID: <20110509082716.GG24068@whitby.uk.xensource.com> (raw)
In-Reply-To: <BANLkTinsZO5ZObUDtEVoTU_SWzW8c6scuQ@mail.gmail.com>
At 16:34 +0100 on 06 May (1304699686), George Dunlap wrote:
> This patch is actually not necessary for the series -- just for the
> verification that it worked. I could drop this patch so we can
> discuss it, and send the other three by themselves (since they seem
> pretty uncontroversial).
I think that's best. I'll be looking at reference-counting p2m entries
soon, I hope, and I'll add some bookkeeping when I do. I suspect I can
isolate it into a single place then.
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
next prev parent reply other threads:[~2011-05-09 8:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 14:01 [PATCH 0 of 4] Use superpages on restore/migrate George Dunlap
2011-05-06 14:01 ` [PATCH 1 of 4] p2m: Keep statistics on order of p2m entries George Dunlap
2011-05-06 14:23 ` Tim Deegan
2011-05-06 15:07 ` George Dunlap
2011-05-06 14:40 ` Christoph Egger
2011-05-06 15:00 ` Tim Deegan
2011-05-06 14:53 ` Christoph Egger
2011-05-06 15:34 ` George Dunlap
2011-05-09 8:27 ` Tim Deegan [this message]
2012-06-08 10:52 ` George Dunlap
2012-06-14 8:52 ` Tim Deegan
2011-05-06 15:14 ` George Dunlap
2011-05-06 14:01 ` [PATCH 2 of 4] tools: Detect superpages on domain restore George Dunlap
2011-05-06 14:01 ` [PATCH 3 of 4] tools: Save superpages in the same batch, to make detection easier George Dunlap
2011-05-06 14:01 ` [PATCH 4 of 4] tools: Introduce "allocate-only" page type for migration George Dunlap
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=20110509082716.GG24068@whitby.uk.xensource.com \
--to=tim.deegan@citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=dunlapg@umich.edu \
--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.