From: Nitin Gupta <nigupta@nvidia.com>
To: Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: RE: [PATCH v2] mm: Proactive compaction
Date: Mon, 2 Mar 2020 21:54:02 +0000 [thread overview]
Message-ID: <BYAPR12MB3015F73999D9C5D4A034DAE2D8E70@BYAPR12MB3015.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200302213343.2712-1-nigupta@nvidia.com>
> -----Original Message-----
> From: Nitin Gupta <nigupta@nvidia.com>
> Sent: Monday, March 2, 2020 1:34 PM
> To: Mel Gorman <mgorman@techsingularity.net>; Michal Hocko
> <mhocko@suse.com>; Vlastimil Babka <vbabka@suse.cz>
> Cc: Nitin Gupta <nigupta@nvidia.com>; Matthew Wilcox
> <willy@infradead.org>; Andrew Morton <akpm@linux-foundation.org>;
> Mike Kravetz <mike.kravetz@oracle.com>; linux-kernel <linux-
> kernel@vger.kernel.org>; linux-mm <linux-mm@kvack.org>
> Subject: [PATCH v2] mm: Proactive compaction
>
> - With 5.6.0-rc3 + this patch, with proactiveness=20
>
> echo 20 | sudo tee /sys/kernel/mm/compaction/node-*/proactiveness
>
> percentile latency
> –––––––––– –––––––
> 5 2
> 10 2
> 25 3
> 30 3
> 40 3
> 50 4
> 60 4
> 75 4
> 80 4
> 90 5
> 95 429
>
The percentile latency data above is correct but the summary line is
Incorrect:
> Total 2M hugepages allocated = 11120 (21.7G worth of hugepages out of 25G
> total free => 98% of free memory could be allocated as hugepages)
>
Corrected:
Total 2M hugepages allocated = 384105 (750G worth of hugepages out of
762G total free => 98% of free memory could be allocated as hugepages)
Thanks,
Nitin
next prev parent reply other threads:[~2020-03-02 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 21:33 Nitin Gupta
2020-03-02 21:54 ` Nitin Gupta [this message]
2020-03-04 18:04 ` Vlastimil Babka
2020-03-04 23:13 ` Nitin Gupta
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=BYAPR12MB3015F73999D9C5D4A034DAE2D8E70@BYAPR12MB3015.namprd12.prod.outlook.com \
--to=nigupta@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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