All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
	George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com, tim@xen.org, jbeulich@suse.com
Subject: Re: [PATCH RESEND RFC 1/8] mm: Separate free page chunk merging into its own routine
Date: Mon, 27 Feb 2017 17:29:41 +0100	[thread overview]
Message-ID: <1488212981.5548.89.camel@citrix.com> (raw)
In-Reply-To: <1488155829-2956-2-git-send-email-boris.ostrovsky@oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 508 bytes --]

On Sun, 2017-02-26 at 19:37 -0500, Boris Ostrovsky wrote:
> This is needed for subsequent changes to memory scrubbing.
> 
So, this is "just" code motion and factorization, right?

If yes, I think the changelog should say so.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-02-27 16:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  0:37 [PATCH RESEND RFC 0/8] Memory scrubbing from idle loop Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 1/8] mm: Separate free page chunk merging into its own routine Boris Ostrovsky
2017-02-27 15:17   ` Andrew Cooper
2017-02-27 16:29   ` Dario Faggioli [this message]
2017-02-27 17:07     ` Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 2/8] mm: Place unscrubbed pages at the end of pagelist Boris Ostrovsky
2017-02-27 15:38   ` Andrew Cooper
2017-02-27 15:52     ` Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 3/8] mm: Scrub pages in alloc_heap_pages() if needed Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 4/8] mm: Scrub memory from idle loop Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 5/8] mm: Do not discard already-scrubbed pages softirqs are pending Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 6/8] spinlock: Introduce _spin_lock_cond() Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 7/8] mm: Keep pages available for allocation while scrubbing Boris Ostrovsky
2017-02-27  0:37 ` [PATCH RESEND RFC 8/8] mm: Print number of unscrubbed pages in 'H' debug handler Boris Ostrovsky
2017-02-27 16:18 ` [PATCH RESEND RFC 0/8] Memory scrubbing from idle loop Andrew Cooper
2017-02-27 17:06   ` Boris Ostrovsky
2017-02-27 18:09     ` Andrew Cooper
2017-03-01 15:48     ` George Dunlap
2017-03-01 16:14       ` Boris Ostrovsky
2017-03-01 16:27         ` Jan Beulich
2017-03-01 16:43           ` Boris Ostrovsky

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=1488212981.5548.89.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.