From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCHv2 2/5] vmscan: Kill hibernation specific reclaim logic and unify it
Date: Mon, 2 Nov 2009 20:03:52 +0100 [thread overview]
Message-ID: <200911022003.52125.rjw@sisk.pl> (raw)
In-Reply-To: <20091103002506.8869.A69D9226@jp.fujitsu.com>
On Monday 02 November 2009, KOSAKI Motohiro wrote:
> > > Then, This patch changed shrink_all_memory() to only the wrapper function of
> > > do_try_to_free_pages(). it bring good reviewability and debuggability, and solve
> > > above problems.
> > >
> > > side note: Reclaim logic unificication makes two good side effect.
> > > - Fix recursive reclaim bug on shrink_all_memory().
> > > it did forgot to use PF_MEMALLOC. it mean the system be able to stuck into deadlock.
> > > - Now, shrink_all_memory() got lockdep awareness. it bring good debuggability.
> >
> > As I said previously, I don't really see a reason to keep shrink_all_memory().
> >
> > Do you think that removing it will result in performance degradation?
>
> Hmm...
> Probably, I misunderstood your mention. I thought you suggested to kill
> all hibernation specific reclaim code. I did. It's no performance degression.
> (At least, I didn't observe)
>
> But, if you hope to kill shrink_all_memory() function itsef, the short answer is,
> it's impossible.
>
> Current VM reclaim code need some preparetion to caller, and there are existing in
> both alloc_pages_slowpath() and try_to_free_pages(). We can't omit its preparation.
Well, my grepping for 'shrink_all_memory' throughout the entire kernel source
code seems to indicate that hibernate_preallocate_memory() is the only current
user of it. I may be wrong, but I doubt it, unless some new users have been
added since 2.6.31.
In case I'm not wrong, it should be safe to drop it from
hibernate_preallocate_memory(), because it's there for performance reasons
only. Now, since hibernate_preallocate_memory() appears to be the only user of
it, it should be safe to drop it entirely.
> Please see following shrink_all_memory() code. it's pretty small. it only have
> few vmscan preparation. I don't think it is hard to maintainance.
No, it's not, but I'm really not sure it's worth keeping.
Thanks,
Rafael
> =====================================================
> unsigned long shrink_all_memory(unsigned long nr_to_reclaim)
> {
> struct reclaim_state reclaim_state;
> struct scan_control sc = {
> .gfp_mask = GFP_HIGHUSER_MOVABLE,
> .may_swap = 1,
> .may_unmap = 1,
> .may_writepage = 1,
> .nr_to_reclaim = nr_to_reclaim,
> .hibernation_mode = 1,
> .swappiness = vm_swappiness,
> .order = 0,
> .isolate_pages = isolate_pages_global,
> };
> struct zonelist * zonelist = node_zonelist(numa_node_id(), sc.gfp_mask);
> struct task_struct *p = current;
> unsigned long nr_reclaimed;
>
> p->flags |= PF_MEMALLOC;
> lockdep_set_current_reclaim_state(sc.gfp_mask);
> reclaim_state.reclaimed_slab = 0;
> p->reclaim_state = &reclaim_state;
>
> nr_reclaimed = do_try_to_free_pages(zonelist, &sc);
>
> p->reclaim_state = NULL;
> lockdep_clear_current_reclaim_state();
> p->flags &= ~PF_MEMALLOC;
>
> return nr_reclaimed;
> }
--
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-11-02 19:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 15:08 [PATCHv2 1/5] vmscan: separate sc.swap_cluster_max and sc.nr_max_reclaim KOSAKI Motohiro
2009-11-01 15:09 ` [PATCHv2 2/5] vmscan: Kill hibernation specific reclaim logic and unify it KOSAKI Motohiro
2009-11-01 15:12 ` Rik van Riel
2009-11-01 21:38 ` Rafael J. Wysocki
2009-11-02 15:35 ` KOSAKI Motohiro
2009-11-02 19:03 ` Rafael J. Wysocki [this message]
2009-11-03 14:00 ` KOSAKI Motohiro
2009-11-03 21:51 ` Rafael J. Wysocki
2009-11-01 22:01 ` Nigel Cunningham
2009-11-02 15:35 ` KOSAKI Motohiro
2009-11-02 19:05 ` Rafael J. Wysocki
2009-11-02 21:19 ` Nigel Cunningham
2009-11-03 11:30 ` Rafael J. Wysocki
2009-11-03 21:12 ` Nigel Cunningham
2009-11-03 22:00 ` Rafael J. Wysocki
2009-11-12 12:33 ` using highmem for atomic copy of lowmem was " Pavel Machek
2009-11-12 23:33 ` Rafael J. Wysocki
2009-11-03 14:00 ` KOSAKI Motohiro
2009-11-03 21:52 ` Rafael J. Wysocki
2009-11-01 15:11 ` [PATCHv2 3/5] vmscan: Stop zone_reclaim()'s wrong swap_cluster_max usage KOSAKI Motohiro
2009-11-01 17:51 ` Rik van Riel
2009-11-02 0:40 ` Minchan Kim
2009-11-01 15:12 ` [PATCHv2 4/5] vmscan: Kill sc.swap_cluster_max KOSAKI Motohiro
2009-11-01 17:56 ` Rik van Riel
2009-11-02 0:46 ` Minchan Kim
2009-11-01 15:13 ` [PATCHv2 5/5][nit fix] vmscan Make consistent of reclaim bale out between do_try_to_free_page and shrink_zone KOSAKI Motohiro
2009-11-01 17:58 ` Rik van Riel
2009-11-02 0:48 ` Minchan Kim
2009-11-02 0:35 ` [PATCHv2 1/5] vmscan: separate sc.swap_cluster_max and sc.nr_max_reclaim Minchan Kim
2009-11-02 0:48 ` Minchan Kim
2009-11-02 15:35 ` KOSAKI Motohiro
2009-11-02 23:34 ` Minchan Kim
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=200911022003.52125.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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