From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com,
MinChan Kim <minchan.kim@gmail.com>,
kamezawa.hiroyu@jp.fujitsu.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, riel@redhat.com
Subject: Re: [PATCH] mm: remove zone->prev_prioriy
Date: Wed, 11 Feb 2009 20:06:46 +0900 (JST) [thread overview]
Message-ID: <20090211195252.C3BD.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20090210151247.6747f66e.akpm@linux-foundation.org>
> On Tue, 10 Feb 2009 19:57:01 +0900
> MinChan Kim <minchan.kim@gmail.com> wrote:
>
> > As you know, prev_priority is used as a measure of how much stress page reclaim.
> > But now we doesn't need it due to split-lru's way.
> >
> > I think it would be better to remain why prev_priority isn't needed any more
> > and how split-lru can replace prev_priority's role in changelog.
> >
> > In future, it help mm newbies understand change history, I think.
>
> Yes, I'd be fascinated to see that explanation.
>
> In http://groups.google.pn/group/linux.kernel/browse_thread/thread/fea9c9a0b43162a1
> it was asserted that we intend to use prev_priority again in the future.
>
> We discussed this back in November:
> http://lkml.indiana.edu/hypermail/linux/kernel/0811.2/index.html#00001
>
> And I think that I still think that the VM got worse due to its (new)
> failure to track previous state. IIRC, the response to that concern
> was quite similar to handwavy waffling.
Yes.
I still think it's valuable code.
I think, In theory, VM sould take parallel reclaim bonus.
However, recently, KAMEZAWA-san reported memcg prev_priority code are
busted due to hierarchical-memory-reclaim and he dislike maintain
unused function.
http://marc.info/?l=linux-mm&m=123258289017433&w=2
and, at that time I can't show good example workload of parallel reclaim bonus
effective.
Therefore I agreed to drop this and insert it again at re-using time ;-)
--
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-11 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 9:42 KOSAKI Motohiro
2009-02-10 10:42 ` Johannes Weiner
2009-02-10 10:50 ` KOSAKI Motohiro
2009-02-10 11:49 ` [PATCH] mm,memcg: remove zone->prev_prioriy take2 KOSAKI Motohiro
2009-02-10 10:57 ` [PATCH] mm: remove zone->prev_prioriy MinChan Kim
2009-02-10 23:12 ` Andrew Morton
2009-02-11 11:06 ` KOSAKI Motohiro [this message]
2009-02-11 11:12 ` Andrew Morton
2009-02-11 11:23 ` KOSAKI Motohiro
2009-02-12 0:00 ` KAMEZAWA Hiroyuki
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=20090211195252.C3BD.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--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