From: "Jörn Engel" <joern@logfs.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: mgorman@suse.de, linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/6] Improving munlock() performance for large non-THP areas
Date: Tue, 6 Aug 2013 12:39:02 -0400 [thread overview]
Message-ID: <20130806163902.GC10535@logfs.org> (raw)
In-Reply-To: <1375713125-18163-1-git-send-email-vbabka@suse.cz>
On Mon, 5 August 2013 16:31:59 +0200, Vlastimil Babka wrote:
>
> timedmunlock
> 3.11-rc3 3.11-rc3 3.11-rc3 3.11-rc3 3.11-rc3 3.11-rc3 3.11-rc3
> 0 1 2 3 4 5 6
> Elapsed min 3.38 ( 0.00%) 3.39 ( -0.14%) 3.00 ( 11.35%) 2.73 ( 19.48%) 2.72 ( 19.50%) 2.34 ( 30.78%) 2.16 ( 36.23%)
> Elapsed mean 3.39 ( 0.00%) 3.39 ( -0.05%) 3.01 ( 11.25%) 2.73 ( 19.54%) 2.73 ( 19.41%) 2.36 ( 30.30%) 2.17 ( 36.00%)
> Elapsed stddev 0.01 ( 0.00%) 0.00 ( 71.98%) 0.01 (-71.14%) 0.00 ( 89.12%) 0.01 (-48.55%) 0.03 (-277.27%) 0.01 (-85.75%)
> Elapsed max 3.41 ( 0.00%) 3.40 ( 0.39%) 3.04 ( 10.81%) 2.73 ( 19.96%) 2.76 ( 19.09%) 2.43 ( 28.64%) 2.20 ( 35.41%)
> Elapsed range 0.02 ( 0.00%) 0.01 ( 74.99%) 0.04 (-66.12%) 0.00 ( 88.12%) 0.03 (-39.24%) 0.09 (-274.85%) 0.04 (-81.04%)
>
>
> Vlastimil Babka (6):
> mm: putback_lru_page: remove unnecessary call to page_lru_base_type()
> mm: munlock: remove unnecessary call to lru_add_drain()
> mm: munlock: batch non-THP page isolation and munlock+putback using
> pagevec
> mm: munlock: batch NR_MLOCK zone state updates
> mm: munlock: bypass per-cpu pvec for putback_lru_page
> mm: munlock: remove redundant get_page/put_page pair on the fast path
>
> mm/mlock.c | 259 ++++++++++++++++++++++++++++++++++++++++++++++++++----------
> mm/vmscan.c | 12 +--
> 2 files changed, 224 insertions(+), 47 deletions(-)
Finally walked through 5/6 as well. The entire patchset looks good to
me. Feel free to attach my Reviewed-By: to the patchset.
JA?rn
--
tglx1 thinks that joern should get a (TM) for "Thinking Is Hard"
-- Thomas Gleixner
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-08-06 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 14:31 [RFC PATCH 0/6] Improving munlock() performance for large non-THP areas Vlastimil Babka
2013-08-05 14:32 ` [RFC PATCH 1/6] mm: putback_lru_page: remove unnecessary call to page_lru_base_type() Vlastimil Babka
2013-08-05 14:32 ` [RFC PATCH 2/6] mm: munlock: remove unnecessary call to lru_add_drain() Vlastimil Babka
2013-08-05 14:32 ` [RFC PATCH 3/6] mm: munlock: batch non-THP page isolation and munlock+putback using pagevec Vlastimil Babka
2013-08-05 17:21 ` Jörn Engel
2013-08-06 13:27 ` Vlastimil Babka
2013-08-06 16:21 ` Jörn Engel
2013-08-05 14:32 ` [RFC PATCH 4/6] mm: munlock: batch NR_MLOCK zone state updates Vlastimil Babka
2013-08-05 17:23 ` Jörn Engel
2013-08-05 14:32 ` [RFC PATCH 5/6] mm: munlock: bypass per-cpu pvec for putback_lru_page Vlastimil Babka
2013-08-05 14:32 ` [RFC PATCH 6/6] mm: munlock: remove redundant get_page/put_page pair on the fast path Vlastimil Babka
2013-08-05 17:31 ` [RFC PATCH 0/6] Improving munlock() performance for large non-THP areas Jörn Engel
2013-08-06 16:39 ` Jörn Engel [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=20130806163902.GC10535@logfs.org \
--to=joern@logfs.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=vbabka@suse.cz \
/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.