From: Shuah Khan <shuahkh@osg.samsung.com>
To: David Rientjes <rientjes@google.com>,
Ben Hutchings <ben@decadent.org.uk>
Cc: linux-api@vger.kernel.org, linux-mm@kvack.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH selftests 5/6] selftests: vm: Try harder to allocate huge pages
Date: Tue, 10 Nov 2015 13:05:51 -0700 [thread overview]
Message-ID: <56424E1F.9040507@osg.samsung.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1511101159480.29993@chino.kir.corp.google.com>
On 11/10/2015 01:01 PM, David Rientjes wrote:
> On Sat, 31 Oct 2015, Ben Hutchings wrote:
>
>> If we need to increase the number of huge pages, drop caches first
>> to reduce fragmentation and then check that we actually allocated
>> as many as we wanted. Retry once if that doesn't work.
>>
>> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
>> ---
>> The test always fails for me in a 1 GB VM without this.
>>
>> Ben.
>>
>> tools/testing/selftests/vm/run_vmtests | 15 ++++++++++++++-
>> 1 file changed, 14 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/testing/selftests/vm/run_vmtests b/tools/testing/selftests/vm/run_vmtests
>> index 9179ce8..97ed1b2 100755
>> --- a/tools/testing/selftests/vm/run_vmtests
>> +++ b/tools/testing/selftests/vm/run_vmtests
>> @@ -20,13 +20,26 @@ done < /proc/meminfo
>> if [ -n "$freepgs" ] && [ -n "$pgsize" ]; then
>> nr_hugepgs=`cat /proc/sys/vm/nr_hugepages`
>> needpgs=`expr $needmem / $pgsize`
>> - if [ $freepgs -lt $needpgs ]; then
>> + tries=2
>> + while [ $tries -gt 0 ] && [ $freepgs -lt $needpgs ]; do
>> lackpgs=$(( $needpgs - $freepgs ))
>> + echo 3 > /proc/sys/vm/drop_caches
>> echo $(( $lackpgs + $nr_hugepgs )) > /proc/sys/vm/nr_hugepages
>> if [ $? -ne 0 ]; then
>> echo "Please run this test as root"
>> exit 1
>> fi
>> + while read name size unit; do
>> + if [ "$name" = "HugePages_Free:" ]; then
>> + freepgs=$size
>> + fi
>> + done < /proc/meminfo
>> + tries=$((tries - 1))
>> + done
>> + if [ $freepgs -lt $needpgs ]; then
>> + printf "Not enough huge pages available (%d < %d)\n" \
>> + $freepgs $needpgs
>> + exit 1
>> fi
>> else
>> echo "no hugetlbfs support in kernel?"
>>
>
> I know this patch is in -mm and hasn't been merged by Linus yet, but I'm
> wondering why the multiple /proc/sys/vm/drop_caches is helping? Would it
> simply suffice to put a sleep in there instead or is drop_caches actually
> doing something useful a second time around?
>
I sent this up for merge in my pull request. Adding sleep would increase
test run-time. Something to keep in mind.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
--
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>
next prev parent reply other threads:[~2015-11-10 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1446334510.2595.13.camel@decadent.org.uk>
2015-10-31 23:39 ` Ben Hutchings
2015-11-10 20:01 ` David Rientjes
2015-11-10 20:05 ` Shuah Khan [this message]
2015-11-10 21:48 ` Ben Hutchings
2015-11-11 1:11 ` David Rientjes
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=56424E1F.9040507@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=ben@decadent.org.uk \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
/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