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 3/8] mm: Scrub pages in alloc_heap_pages() if needed
Date: Sat, 22 Jul 2017 22:07:25 -0400 [thread overview]
Message-ID: <483b5e10-bc61-1ebc-c7bd-1708d8458c65@oracle.com> (raw)
In-Reply-To: <59529D5302000078001014F7@prv-mh.provo.novell.com>
On 06/27/2017 02:00 PM, Jan Beulich wrote:
>>>> Boris Ostrovsky <boris.ostrovsky@oracle.com> 06/22/17 8:55 PM >>>
>> @@ -862,10 +879,19 @@ static struct page_info *alloc_heap_pages(
>> if ( d != NULL )
>> d->last_alloc_node = node;
>>
>> + need_scrub = !!first_dirty_pg && !(memflags & MEMF_no_scrub);
>
> No need for !! here. But I wonder whether that part of the check is really
> useful anyway, considering the sole use ...
>
>> for ( i = 0; i < (1 << order); i++ )
>> {
>> /* Reference count must continuously be zero for free pages. */
>> - BUG_ON(pg[i].count_info != PGC_state_free);
>> + BUG_ON((pg[i].count_info & ~PGC_need_scrub) != PGC_state_free);
>> +
>> + if ( test_bit(_PGC_need_scrub, &pg[i].count_info) )
>> + {
>> + if ( need_scrub )
>> + scrub_one_page(&pg[i]);
>
> ... here. If it isn't, I think the local variable isn't warranted either.
> If you agree, the thus adjusted patch can have
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> (otherwise I'll wait with it to understand the reason first).
first_dirty_pg is indeed unnecessary but I think local variable is
useful to avoid ANDing memflags inside the loop on each iteration
(unless you think compiler is smart enough to realize that memflags is
not changing).
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-23 2:07 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 [this message]
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
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=483b5e10-bc61-1ebc-c7bd-1708d8458c65@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.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 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).