From: MinChan Kim <minchan.kim@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>,
William Lee Irwin III <wli@movementarian.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] vmscan: initialize sc->nr_reclaimed in do_try_to_free_pages()
Date: Tue, 10 Feb 2009 21:31:04 +0900 [thread overview]
Message-ID: <28c262360902100431l4a5977e7p9c5152882f09dcf9@mail.gmail.com> (raw)
In-Reply-To: <20090210210520.7004.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Tue, Feb 10, 2009 at 9:06 PM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
>> > static int __zone_reclaim(struct zone *zone, gfp_t gfp_mask, unsigned int order)
>> > {
>> > /* Minimum pages needed in order to stay on node */
>> > const unsigned long nr_pages = 1 << order;
>> > struct task_struct *p = current;
>> > struct reclaim_state reclaim_state;
>> > int priority;
>> > struct scan_control sc = {
>> > .may_writepage = !!(zone_reclaim_mode & RECLAIM_WRITE),
>> > .may_swap = !!(zone_reclaim_mode & RECLAIM_SWAP),
>> > .swap_cluster_max = max_t(unsigned long, nr_pages,
>> > SWAP_CLUSTER_MAX),
>> > .gfp_mask = gfp_mask,
>> > .swappiness = vm_swappiness,
>> > .isolate_pages = isolate_pages_global,
>> > + .nr_reclaimed = 0;
>> > };
>>
>> Hmm.. I missed that. Thanks.
>> There is one in shrink_all_memory.
>
> No.
> __zone_reclaim isn't a part of shrink_all_memory().
> Currently, shrink_all_memory() don't use sc.nr_reclaimed member.
> (maybe, it's another wrong thing ;)
Hmm.. You're right.
As Johannes pointed out,
too many page shrinking can degrade resume performance.
We need to bale out in shrink_all_memory.
Other people, thought ?
--
Kinds regards,
MinChan Kim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-10 12:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 22:24 [RFC] vmscan: initialize sc->nr_reclaimed in do_try_to_free_pages() Johannes Weiner
2009-02-10 10:47 ` MinChan Kim
2009-02-10 11:43 ` KOSAKI Motohiro
2009-02-10 12:03 ` MinChan Kim
2009-02-10 12:06 ` KOSAKI Motohiro
2009-02-10 12:31 ` MinChan Kim [this message]
2009-02-10 12:35 ` KOSAKI Motohiro
2009-02-10 12:40 ` MinChan Kim
2009-02-10 12:58 ` [PATCH] vmscan: initialize sc->nr_reclaimed properly take2 KOSAKI Motohiro
2009-02-10 13:00 ` [PATCH] shrink_all_memory() use sc.nr_reclaimed KOSAKI Motohiro
2009-02-10 16:20 ` Johannes Weiner
2009-02-10 20:41 ` KOSAKI Motohiro
2009-02-11 0:37 ` MinChan Kim
2009-02-11 11:50 ` KOSAKI Motohiro
2009-02-11 12:43 ` MinChan Kim
2009-02-11 12:58 ` KOSAKI Motohiro
2009-02-11 13:03 ` KOSAKI Motohiro
2009-02-10 16:09 ` [PATCH] vmscan: initialize sc->nr_reclaimed properly take2 Johannes Weiner
2009-02-10 22:06 ` Andrew Morton
2009-02-10 22:15 ` Johannes Weiner
2009-02-11 10:52 ` KOSAKI Motohiro
2009-02-10 22:16 ` [RFC] vmscan: initialize sc->nr_reclaimed in do_try_to_free_pages() Andrew Morton
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=28c262360902100431l4a5977e7p9c5152882f09dcf9@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=wli@movementarian.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;
as well as URLs for NNTP newsgroup(s).