xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "rshriram@cs.ubc.ca" <rshriram@cs.ubc.ca>,
	Jim Fehlig <jfehlig@novell.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH 0 of 8] Remove static variables from xc_domain_{save, restore}.c
Date: Tue, 24 May 2011 18:52:55 +0100	[thread overview]
Message-ID: <1306259575.7348.3.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <19931.58561.758368.326386@mariner.uk.xensource.com>

On Tue, 2011-05-24 at 18:02 +0100, Ian Jackson wrote:
> Shriram Rajagopalan writes ("[Xen-devel] Re: [PATCH 0 of 8] Remove static variables from xc_domain_{save, restore}.c"):
> > I ll do it!!.. I have been waiting for this. Thanks a lot for
> > cleaning up this chaff!  I was under the impression that this was
> > some arcane legacy code that shouldnt be touched.
> 
> No, it's arcane legacy code that we have been gradually cleaning up
> :-).
> 
> > One particular
> > thing that I would like to do is to factor out the write functions
> > (outbuf_*, noncached_write, ratewrite*, etc) into a separate file
> > and make it sort of pluggable.
> 
> Do you have a particular use case fot that ?  Without a different set
> of implementations I'm not sure that we need it to be pluggable.
> 
> > (selfish :P) I wanted to introduce a patch that would overlap outbuf
> > flush operation and guest memory copy operation instead of the
> > current model <flush,copy,flush,copy..>.  This might be helpful for
> > both Remus and live migration of large domains.
> 
> But yes, if that produces a speedup, certainly.
> 
> >  Shriram, does this have any impact on Remus?
> 
> I think it should be OK but we should hear what Shriram has to say
> (CC'd).

You were replying to Shriram ;-)

Ian.

  reply	other threads:[~2011-05-24 17:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24  9:14 [PATCH 0 of 8] Remove static variables from xc_domain_{save, restore}.c Ian Campbell
2011-05-24  9:14 ` [PATCH 1 of 8] libxc: save/restore: remove static context variables Ian Campbell
2011-05-24 10:33   ` Vincent Hanquez
2011-05-24  9:14 ` [PATCH 2 of 8] libxc: save: drop code under ADAPTIVE_SAVE ifdef Ian Campbell
2011-05-24  9:14 ` [PATCH 3 of 8] libxc: save: rename ratewrite to uncached Ian Campbell
2011-05-24  9:14 ` [PATCH 4 of 8] libxc: save: noncached write doesn't use live parameter Ian Campbell
2011-05-24  9:14 ` [PATCH 5 of 8] libxc: save: move static "write_count" variable into outbuf Ian Campbell
2011-05-24  9:14 ` [PATCH 6 of 8] libxc: save: encapsulate time stats in a struct Ian Campbell
2011-05-24  9:14 ` [PATCH 7 of 8] libxc: save: don't bother calculating stat's deltas unless we are going to print them Ian Campbell
2011-05-24  9:14 ` [PATCH 8 of 8] libxc: save: move static stats variable to stack variable Ian Campbell
2011-05-24 16:45   ` Ian Jackson
2011-05-24 13:47 ` [PATCH 0 of 8] Remove static variables from xc_domain_{save, restore}.c Shriram Rajagopalan
2011-05-24 17:02   ` Ian Jackson
2011-05-24 17:52     ` Ian Campbell [this message]
2011-05-24 18:57       ` Shriram Rajagopalan

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=1306259575.7348.3.camel@dagon.hellion.org.uk \
    --to=ian.campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jfehlig@novell.com \
    --cc=rshriram@cs.ubc.ca \
    --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).