From: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
To: Eric B Munson <emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
Cc: Sri Jayaramappa
<sjayaram-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>,
Shuah Khan <shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V2] Test compaction of mlocked memory
Date: Thu, 23 Apr 2015 13:23:23 -0700 [thread overview]
Message-ID: <20150423132323.a3bd1dcdc94a2da3ca06a30d@linux-foundation.org> (raw)
In-Reply-To: <20150423184134.GF2282-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
On Thu, 23 Apr 2015 14:41:34 -0400 Eric B Munson <emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org> wrote:
> On Thu, 23 Apr 2015, Sri Jayaramappa wrote:
>
> > Commit commit 5bbe3547aa3b ("mm: allow compaction of unevictable pages")
> > introduced a sysctl that allows userspace to enable scanning of locked
> > pages for compaction. This patch introduces a new test which fragments
> > main memory and attempts to allocate a number of huge pages to exercise
> > this compaction logic.
> >
> > Tested on machines with up to 32 GB RAM. With the patch a much larger
> > number of huge pages can be allocated than on the kernel without the
> > patch.
> >
> > Example output:
> > On a machine with 16 GB RAM:
> > sudo make run_tests vm
> > ...
> > -----------------------
> > running compaction_test
> > -----------------------
> > No of huge pages allocated = 3834
> > [PASS]
> > ...
> >
> > Signed-off-by: Sri Jayaramappa <sjayaram-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
> > Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > Cc: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > Cc: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
> > Cc: Eric B Munson <emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
>
> Reviewed-by: Eric B Munson <emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
Acked-by: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
I'm assuming that Shuah will process this one?
next prev parent reply other threads:[~2015-04-23 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 18:21 [PATCH V2] Test compaction of mlocked memory Sri Jayaramappa
[not found] ` <1429813301-27216-1-git-send-email-sjayaram-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-04-23 18:41 ` Eric B Munson
[not found] ` <20150423184134.GF2282-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-04-23 20:23 ` Andrew Morton [this message]
2015-04-23 20:24 ` Shuah Khan
[not found] ` <553954FC.4050700-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-05-06 17:01 ` Shuah Khan
[not found] ` <554A4904.4040604-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-05-06 17:28 ` Sri
[not found] ` <554A4F50.6080208-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-05-06 17:41 ` Shuah Khan
[not found] ` <554A525A.8000401-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-05-06 17:44 ` Sri
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=20150423132323.a3bd1dcdc94a2da3ca06a30d@linux-foundation.org \
--to=akpm-de/tnxtf+jlsfhdxvbkv3wd2fqjk+8+b@public.gmane.org \
--cc=emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org \
--cc=sjayaram-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.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).