From: Minchan Kim <minchan.kim@gmail.com>
To: Alex Shi <alex.shi@intel.com>
Cc: majordomo@kvack.org, P@draigBrady.com, mgorman@suse.de,
linux-kernel@vger.kernel.org, andrea@cpushare.com,
tim.c.chen@intel.com, shaohua.li@intel.com,
akpm@linux-foundation.org, riel@redhat.com, luto@mit.edu
Subject: Re: [PATCH] kswapd: assign new_order and new_classzone_idx after wakeup in sleeping
Date: Fri, 29 Jul 2011 17:57:17 +0900 [thread overview]
Message-ID: <20110729085717.GC1843@barrios-desktop> (raw)
In-Reply-To: <1311903282-8539-1-git-send-email-alex.shi@intel.com>
On Fri, Jul 29, 2011 at 09:34:42AM +0800, Alex Shi wrote:
> There 2 place to read pgdat in kswapd. One is return from a successful
> balance, another is waked up from sleeping. But the new_order and
> new_classzone_idx are not assigned after kswapd_try_to_sleep(), that
> will cause a bug in the following scenario.
>
> After the last time successful balance, kswapd goes to sleep. So the
> new_order and new_classzone_idx were assigned to 0 and MAX-1 since there
> is no new wakeup during last time balancing. Now, a new wakeup came and
> finish balancing successful with order > 0. But since new_order is still
> 0, this time successful balancing were judged as a failed balance. so,
> if there is another new wakeup coming during balancing, kswapd cann't
> read this and still want to try to sleep. And if the new wakeup is a
> tighter request, kswapd may goes to sleep, not to do balancing. That is
> incorrect.
>
> So, to avoid above problem, the new_order and new_classzone_idx need to
> be assigned for later successful comparison.
>
> Paidrag Brady, Could like do a retry for your problem on this patch?
>
> Signed-off-by: Alex Shi <alex.shi@intel.com>
> Acked-by: Mel Gorman <mgorman@suse.de>
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2011-07-29 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 1:34 Alex Shi
2011-07-29 8:57 ` Minchan Kim [this message]
2011-07-29 15:33 ` Shi, Alex
-- strict thread matches above, loose matches on Subject: below --
2011-07-29 1:45 Alex Shi
2011-07-28 8:11 Alex Shi
2011-07-28 10:19 ` Mel Gorman
2011-07-28 10:47 ` Alex,Shi
2011-07-28 11:12 ` Mel Gorman
2011-07-29 0:10 ` Alex,Shi
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=20110729085717.GC1843@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=P@draigBrady.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=andrea@cpushare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=majordomo@kvack.org \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.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
all inboxes | Powered by JetHome®