All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Felipe Franciosi <felipe@nutanix.com>
Cc: Juan Quintela <quintela@redhat.com>,
	"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
	amit Shah <amit.shah@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Malcolm Crossley <malcolm@nutanix.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/4] migration: set dirty_pages_rate before autoconverge logic
Date: Thu, 25 May 2017 19:10:58 +0800	[thread overview]
Message-ID: <20170525111058.GC22816@pxdev.xzpeter.org> (raw)
In-Reply-To: <3F052E47-5144-411B-BBEF-03C0E4D872B7@nutanix.com>

On Thu, May 25, 2017 at 10:52:32AM +0000, Felipe Franciosi wrote:
> 
> > On 25 May 2017, at 01:40, Peter Xu <peterx@redhat.com> wrote:
> > 
> > On Wed, May 24, 2017 at 05:10:01PM +0100, Felipe Franciosi wrote:
> >> Currently, a "period" in the RAM migration logic is at least a second
> >> long and accounts for what happened since the last period (or the
> >> beginning of the migration). The dirty_pages_rate counter is calculated
> >> at the end this logic.
> >> 
> >> If the auto convergence capability is enabled from the start of the
> >> migration, it won't be able to use this counter the first time around.
> >> This calculates dirty_pages_rate as soon as a period is deemed over,
> >> which allows for it to be used immediately.
> >> 
> >> Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
> > 
> > You fixed the indents as well, but imho it's okay.
> 
> Yeah a couple of lines were off-by-one space. Fixed it given I was touching the code anyway, hope it's ok with everyone else. Would you normally patch that separately or just mention it in the commit message?

For me normally I don't intentionally touch code up only for
indentation to make sure commit log won't be affected for those lines.
However I'm also okay if we fix some of them, either separately or
squashed into patch like this.

IMHO at last it really depends on the maintainers' flavor on this. :-)

Thanks,

-- 
Peter Xu

  reply	other threads:[~2017-05-25 11:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 16:09 [Qemu-devel] [PATCH 0/4] migration: autoconverge counter fixes Felipe Franciosi
2017-05-24 16:10 ` [Qemu-devel] [PATCH 1/4] migration: keep bytes_xfer_prev init'd to zero Felipe Franciosi
2017-05-25  0:50   ` Peter Xu
2017-05-30 16:14   ` Juan Quintela
2017-05-24 16:10 ` [Qemu-devel] [PATCH 2/4] migration: set dirty_pages_rate before autoconverge logic Felipe Franciosi
2017-05-25  0:40   ` Peter Xu
2017-05-25 10:52     ` Felipe Franciosi
2017-05-25 11:10       ` Peter Xu [this message]
2017-05-30 16:14   ` Juan Quintela
2017-05-24 16:10 ` [Qemu-devel] [PATCH 3/4] migration: set bytes_xfer_* outside of " Felipe Franciosi
2017-05-25  0:40   ` Peter Xu
2017-05-30 16:14   ` Juan Quintela
2017-05-24 16:10 ` [Qemu-devel] [PATCH 4/4] migration: use dirty_rate_high_cnt more aggressively Felipe Franciosi
2017-05-24 16:25   ` Daniel P. Berrange
2017-05-24 16:36     ` Felipe Franciosi
2017-05-25  1:03   ` Peter Xu
2017-05-25 11:20     ` Felipe Franciosi
2017-05-26  2:45       ` Peter Xu
2017-05-30 16:17   ` Juan Quintela

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=20170525111058.GC22816@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=felipe@nutanix.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=malcolm@nutanix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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.