From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
George Dunlap <george.dunlap@citrix.com>
Cc: tim@xen.org, sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH RESEND RFC 0/8] Memory scrubbing from idle loop
Date: Wed, 1 Mar 2017 11:43:54 -0500 [thread overview]
Message-ID: <6a9cb5f5-162e-fbfe-447c-075b509ba680@oracle.com> (raw)
In-Reply-To: <58B70490020000780013EE2F@prv-mh.provo.novell.com>
On 03/01/2017 11:27 AM, Jan Beulich wrote:
>>>> On 01.03.17 at 17:14, <boris.ostrovsky@oracle.com> wrote:
>> On 03/01/2017 10:48 AM, George Dunlap wrote:
>>> On 27/02/17 17:06, Boris Ostrovsky wrote:
>>>> Since dirty pages are always at the tail of page lists we are not really
>>>> searching the lists. As soon as a clean page is found (starting from the
>>>> tail) we can stop.
>>> Sure, having a back and a front won't add significant overhead; but it
>>> does make things a bit strange. What does it buy us over having two lists?
>> If we implement dirty heap just like we do regular heap (i.e.
>> node/zone/order) that datastructure is almost a megabyte under current
>> assumptions (i.e. sizeof(page_list_head) * MAX_NUMNODES * NR_ZONES *
>> (MAX_ORDER+1) = 16 * 41 * 21 * 64 = 881664).
> Furthermore I'd be afraid for this to move us further away from
> being able to recombine higher order buddies early.
Possibly, although we would still be combining within each of the two heaps.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-03-01 16:43 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
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 [this message]
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=6a9cb5f5-162e-fbfe-447c-075b509ba680@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@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).