linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: Vijay Balakrishna <vijayb@linux.microsoft.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Oleg Nesterov <oleg@redhat.com>, Song Liu <songliubraving@fb.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Michal Hocko <mhocko@suse.com>, Allen Pais <apais@microsoft.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [v1] mm: khugepaged: avoid overriding min_free_kbytes set by user
Date: Tue, 15 Sep 2020 14:27:34 -0400	[thread overview]
Message-ID: <CA+CK2bDH-BGAWhCYLpsxwhS1+eHibqmjLiXAhyr0i94YJspYuA@mail.gmail.com> (raw)
In-Reply-To: <1600145748-26518-1-git-send-email-vijayb@linux.microsoft.com>

On Tue, Sep 15, 2020 at 12:55 AM Vijay Balakrishna
<vijayb@linux.microsoft.com> wrote:
>
> set_recommended_min_free_kbytes need to honor min_free_kbytes set by the
> user.  Post start-of-day THP enable or memory hotplug operations can
> lose user specified min_free_kbytes, in particular when it is higher than
> calculated recommended value.
>
> Signed-off-by: Vijay Balakrishna <vijayb@linux.microsoft.com>
> Cc: stable@vger.kernel.org
> ---
>  mm/khugepaged.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 4f7107476a6f..b4b753ba411a 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -2253,7 +2253,7 @@ static void set_recommended_min_free_kbytes(void)
>  {
>         struct zone *zone;
>         int nr_zones = 0;
> -       unsigned long recommended_min;
> +       int recommended_min;

Hi Vijay,

Please explain in log the type change. user_min_free_kbytes is  of
"int" type and is initialized to -1, so comparing to unsigned leads to
undesired effect.


>
>         for_each_populated_zone(zone) {
>                 /*
> @@ -2280,12 +2280,12 @@ static void set_recommended_min_free_kbytes(void)
>
>         /* don't ever allow to reserve more than 5% of the lowmem */
>         recommended_min = min(recommended_min,
> -                             (unsigned long) nr_free_buffer_pages() / 20);
> +                             (int) nr_free_buffer_pages() / 20);
>         recommended_min <<= (PAGE_SHIFT-10);
>
> -       if (recommended_min > min_free_kbytes) {
> +       if (recommended_min > user_min_free_kbytes) {

Took me a while to understand, but this change is correct. It is the
same logic that is done in init_per_zone_wmark_min().

Please join the two patches you have in one patch series.
Reviewed-by: Pavel Tatashin <pasha.tatashin@soleen.com>

Thank you,
Pasha

  reply	other threads:[~2020-09-15 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15  4:55 [v1] mm: khugepaged: avoid overriding min_free_kbytes set by user Vijay Balakrishna
2020-09-15 18:27 ` Pavel Tatashin [this message]
2020-09-15 19:31   ` Vijay Balakrishna

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=CA+CK2bDH-BGAWhCYLpsxwhS1+eHibqmjLiXAhyr0i94YJspYuA@mail.gmail.com \
    --to=pasha.tatashin@soleen.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=apais@microsoft.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=oleg@redhat.com \
    --cc=songliubraving@fb.com \
    --cc=vijayb@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).