linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: DaeRo Lee <skseofh@gmail.com>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmscan.c: no need to double-check if free pages are under high-watermark
Date: Sat, 26 Mar 2022 15:50:22 +0000	[thread overview]
Message-ID: <20220326155022.6pqxcfazjaw47eu5@master> (raw)
In-Reply-To: <20220106125758.GY3366@techsingularity.net>

On Thu, Jan 06, 2022 at 12:57:58PM +0000, Mel Gorman wrote:
>On Thu, Jan 06, 2022 at 09:03:34PM +0900, DaeRo Lee wrote:
>> > > @@ -4355,7 +4355,7 @@ static enum zone_type kswapd_highest_zoneidx(pg_data_t *pgdat,
>> > >  static void kswapd_try_to_sleep(pg_data_t *pgdat, int alloc_order, int reclaim_order,
>> > >                               unsigned int highest_zoneidx)
>> > >  {
>> > > -     long remaining = 0;
>> > > +     long remaining = ~0;
>> > >       DEFINE_WAIT(wait);
>> > >
>> > >       if (freezing(current) || kthread_should_stop())
>> >
>> > While this does avoid calling prepare_kswapd_sleep() twice if the pgdat
>> > is balanced on the first try, it then does not restore the vmstat
>> > thresholds and doesn't call schedul() for kswapd to go to sleep.
>> 
>> I intended not to call prepare_kswapd_sleep() twice when the pgdat is NOT
>> balanced on the first try:)
>> 
>
>Stupid typo on my part.
>
>> > @@ -4406,11 +4412,11 @@ static void kswapd_try_to_sleep(pg_data_t *pgdat, int alloc_order, int reclaim_o
>> >         }
>> >
>> >         /*
>> > -        * After a short sleep, check if it was a premature sleep. If not, then
>> > -        * go fully to sleep until explicitly woken up.
>> > +        * If balanced to the high watermark, restore vmstat thresholds and
>> > +        * kswapd goes to sleep. If kswapd remains awake, account whether
>> > +        * the low or high watermark was hit quickly.
>> >          */
>> > -       if (!remaining &&
>> > -           prepare_kswapd_sleep(pgdat, reclaim_order, highest_zoneidx)) {
>> > +       if (balanced) {
>> >                 trace_mm_vmscan_kswapd_sleep(pgdat->node_id);
>> >
>> >                 /*
>> 
>> But, I think what you did is more readable and nice.
>> Thanks!
>> 
>
>Feel free to pick it up, rerun your tests to ensure it's behaving as
>expected and resend! Include something in the changelog about user-visible
>effects if any (or a note saying that it reduces unnecssary overhead)
>and resend with me added to the cc.
>

Hi, All

Seems this thread stops here. I don't see following patch and current upstream
doesn't include this change.

May I continue this? Of course, with author-ship from DaeRo Lee <skseofh@gmail.com>.

Mel,

Would you mind suggesting some cases that I could do to see the effects from
this change? Such as the overhead or throughput? Or what cases you expect?


-- 
Wei Yang
Help you, Help me


  reply	other threads:[~2022-03-26 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02  3:31 [PATCH] mm/vmscan.c: no need to double-check if free pages are under high-watermark skseofh
2022-01-06  0:17 ` Andrew Morton
2022-01-06  9:46 ` Mel Gorman
2022-01-06 12:03   ` DaeRo Lee
2022-01-06 12:57     ` Mel Gorman
2022-03-26 15:50       ` Wei Yang [this message]
2022-04-07 13:56         ` Mel Gorman

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=20220326155022.6pqxcfazjaw47eu5@master \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=skseofh@gmail.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).