From: Ebru Akagunduz <ebru.akagunduz@gmail.com>
To: linux-mm@kvack.org
Cc: hughd@google.com, riel@redhat.com, akpm@linux-foundation.org,
kirill.shutemov@linux.intel.com, n-horiguchi@ah.jp.nec.com,
aarcange@redhat.com, iamjoonsoo.kim@lge.com, gorcunov@openvz.org,
linux-kernel@vger.kernel.org, mgorman@suse.de,
rientjes@google.com, vbabka@suse.cz,
aneesh.kumar@linux.vnet.ibm.com, hannes@cmpxchg.org,
mhocko@suse.cz, boaz@plexistor.com, minchan@kernel.org
Subject: Re: [RFC PATCH 3/3] doc: add information about min_ptes_young
Date: Mon, 13 Jun 2016 21:37:07 +0300 [thread overview]
Message-ID: <20160613183707.GD3815@debian> (raw)
In-Reply-To: <1465672561-29608-4-git-send-email-ebru.akagunduz@gmail.com>
On Sat, Jun 11, 2016 at 10:16:01PM +0300, Ebru Akagunduz wrote:
> min_ptes_young specifies at least how many young pages needed
> to create a THP. This threshold also effects when making swapin
> readahead (if needed) to create a THP. We decide whether to make
> swapin readahed wortwhile looking the value.
>
> /sys/kernel/mm/transparent_hugepage/khugepaged/min_ptes_young
>
> Signed-off-by: Ebru Akagunduz <ebru.akagunduz@gmail.com>
Suggested-by: Minchan Kim <minchan@kernel.org>
> ---
Cc'ed Minchan Kim.
> Documentation/vm/transhuge.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt
> index 2ec6adb..0ae713b 100644
> --- a/Documentation/vm/transhuge.txt
> +++ b/Documentation/vm/transhuge.txt
> @@ -193,6 +193,13 @@ memory. A lower value can prevent THPs from being
> collapsed, resulting fewer pages being collapsed into
> THPs, and lower memory access performance.
>
> +min_ptes_young specifies at least how many young pages needed
> +to create a THP. This threshold also effects when making swapin
> +readahead (if needed) to create a THP. We decide whether to make
> +swapin readahed wortwhile looking the value.
> +
> +/sys/kernel/mm/transparent_hugepage/khugepaged/min_ptes_young
> +
> == Boot parameter ==
>
> You can change the sysfs boot time defaults of Transparent Hugepage
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-06-13 18:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 19:15 [RFC PATCH 0/3] mm, thp: convert from optimistic to conservative Ebru Akagunduz
2016-06-11 19:15 ` [RFC PATCH 1/3] mm, thp: revert allocstall comparing Ebru Akagunduz
2016-06-13 18:32 ` Ebru Akagunduz
2016-06-14 7:07 ` Michal Hocko
2016-06-11 19:16 ` [RFC PATCH 2/3] mm, thp: convert from optimistic to conservative Ebru Akagunduz
2016-06-13 18:35 ` Ebru Akagunduz
2016-06-14 7:18 ` Michal Hocko
2016-06-15 6:40 ` Minchan Kim
2016-06-16 9:08 ` Ebru Akagunduz
2016-06-11 19:16 ` [RFC PATCH 3/3] doc: add information about min_ptes_young Ebru Akagunduz
2016-06-13 18:37 ` Ebru Akagunduz [this message]
2016-06-13 18:30 ` [RFC PATCH 0/3] mm, thp: convert from optimistic to conservative Ebru Akagunduz
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=20160613183707.GD3815@debian \
--to=ebru.akagunduz@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=boaz@plexistor.com \
--cc=gorcunov@openvz.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=minchan@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--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 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).