linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: MinChan Kim <minchan.kim@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	riel@redhat.com
Subject: Re: Question: Is  zone->prev_prirotiy  used ?
Date: Thu, 22 Jan 2009 09:15:32 +0900	[thread overview]
Message-ID: <20090122001532.GC17969@barrios-desktop> (raw)
In-Reply-To: <20090122090657.7c1d7b56.kamezawa.hiroyu@jp.fujitsu.com>

On Thu, Jan 22, 2009 at 09:06:57AM +0900, KAMEZAWA Hiroyuki wrote:
> On Thu, 22 Jan 2009 08:54:07 +0900 (JST)
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> 
> > > On Wed, Jan 21, 2009 at 03:52:19PM +0900, KAMEZAWA Hiroyuki wrote:
> > > > Just a question.
> > > > 
> > > > In vmscan.c,  zone->prev_priority doesn't seem to be used.
> > > > 
> > > > Is it for what, now ?
> > > 
> > > It's the purpose of reclaiming mapped pages before split-lru.
> > > Now, get_scan_ratio can do it. 
> > > I think it is a meaningless variable.
> > > How about Kosaki and Rik ?
> > 
> > Right.
> > I thought this variable can use for future enhancement. 
> > then I didn't removed.
> > 
> example ?
> 
> > Kamezawa-san, does its variable prevent your development?
> > if so, I don't oppose removing.
> > 
> 
> Hmm, I tried to fix/clean up hierarchical-memory-reclaim + split-LRU and
> wondered where prev_priority should be recorded (hierarchy root or local or..)
> and found prev_priority is not used.
> 
> IMHO, LRU management is too complex to keep unnecessary code maintained just
> because it may be used in future. I personally like to rewrite better new code
> rather than reuse old ruins.

I agree. It's too complicated. 
I think it would be better to remove it. 
We can insert it again when we will really need it. 
 
> But I'm not in hurry. I just wanted to confirm.
> 
> BTW, I noticed mem_cgroup_calc_mapped_ratio() is not used, either ;)
> 
> Thanks,
> -Kame

--
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>

  reply	other threads:[~2009-01-22  0:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  6:52 KAMEZAWA Hiroyuki
2009-01-21  7:17 ` MinChan Kim
2009-01-21 23:54   ` KOSAKI Motohiro
2009-01-22  0:06     ` KAMEZAWA Hiroyuki
2009-01-22  0:15       ` MinChan Kim [this message]
2009-01-23  3:22       ` KOSAKI Motohiro

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=20090122001532.GC17969@barrios-desktop \
    --to=minchan.kim@gmail.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --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