From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: tim@xen.org, sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v5 0/8] Memory scrubbing from idle loop
Date: Fri, 23 Jun 2017 09:11:16 -0400 [thread overview]
Message-ID: <042022ac-db2b-f8ab-0cec-456c0c70a1cb@oracle.com> (raw)
In-Reply-To: <594CFD2102000078001662A8@prv-mh.provo.novell.com>
On 06/23/2017 05:36 AM, Jan Beulich wrote:
>>>> On 22.06.17 at 20:57, <boris.ostrovsky@oracle.com> wrote:
>> Deferred:
>> * Per-node heap locks. In addition to (presumably) improving performance in
>> general, once they are available we can parallelize scrubbing further by
>> allowing more than one core per node to do idle loop scrubbing.
>
> I don't understand: A per-node lock still calls for just one CPU
> doing the scrubbing on that node, in order to not congest the
> lock.
Is this necessarily true? Maybe not allow all cores on a node to scrub
but I'd think having more than one core do the work may be beneficial.
Don't forget that actual scrubbing is performed without holding locks.
We only grab the lock to find dirty buddies in the heap.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-23 13:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 18:57 [PATCH v5 0/8] Memory scrubbing from idle loop Boris Ostrovsky
2017-06-22 18:57 ` [PATCH v5 1/8] mm: Place unscrubbed pages at the end of pagelist Boris Ostrovsky
2017-06-27 17:06 ` Jan Beulich
2017-07-23 2:00 ` Boris Ostrovsky
2017-07-31 14:45 ` Jan Beulich
2017-07-31 16:03 ` Boris Ostrovsky
2017-08-02 9:24 ` Jan Beulich
2017-08-02 15:31 ` Boris Ostrovsky
2017-06-22 18:57 ` [PATCH v5 2/8] mm: Extract allocation loop from alloc_heap_pages() Boris Ostrovsky
2017-06-27 17:59 ` Jan Beulich
2017-06-22 18:57 ` [PATCH v5 3/8] mm: Scrub pages in alloc_heap_pages() if needed Boris Ostrovsky
2017-06-27 18:00 ` Jan Beulich
2017-07-23 2:07 ` Boris Ostrovsky
2017-07-31 15:16 ` Jan Beulich
2017-07-31 16:07 ` Boris Ostrovsky
2017-06-22 18:57 ` [PATCH v5 4/8] mm: Scrub memory from idle loop Boris Ostrovsky
2017-06-23 8:36 ` Dario Faggioli
2017-06-27 18:01 ` Jan Beulich
2017-07-23 2:14 ` Boris Ostrovsky
2017-07-31 15:20 ` Jan Beulich
2017-07-31 16:15 ` Boris Ostrovsky
2017-08-02 9:27 ` Jan Beulich
2017-06-22 18:57 ` [PATCH v5 5/8] spinlock: Introduce spin_lock_cb() Boris Ostrovsky
2017-06-22 18:57 ` [PATCH v5 6/8] mm: Keep heap accessible to others while scrubbing Boris Ostrovsky
2017-06-27 19:28 ` Jan Beulich
2017-06-27 19:31 ` Jan Beulich
2017-07-23 2:28 ` Boris Ostrovsky
2017-08-02 8:34 ` Jan Beulich
2017-06-22 18:57 ` [PATCH v5 7/8] mm: Print number of unscrubbed pages in 'H' debug handler Boris Ostrovsky
2017-06-22 18:57 ` [PATCH v5 8/8] mm: Make sure pages are scrubbed Boris Ostrovsky
2017-06-27 19:29 ` Jan Beulich
2017-06-23 9:36 ` [PATCH v5 0/8] Memory scrubbing from idle loop Jan Beulich
2017-06-23 13:11 ` Boris Ostrovsky [this message]
2017-06-23 13:22 ` Jan Beulich
2017-06-23 13:29 ` 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=042022ac-db2b-f8ab-0cec-456c0c70a1cb@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.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 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).