From: Andrew Morton <akpm@linux-foundation.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>,
Minchan Kim <minchan.kim@gmail.com>,
Hugh Dickins <hughd@google.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] tmpfs: Insert tmpfs cache pages to inactive list at first
Date: Fri, 21 May 2010 17:32:15 -0400 [thread overview]
Message-ID: <20100521173215.e2240f5b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100522085421.1E72.A69D9226@jp.fujitsu.com>
On Sat, 22 May 2010 09:04:30 +0900 (JST) KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> > > -static inline void lru_cache_add_active_anon(struct page *page)
> > > -{
> > > - __lru_cache_add(page, LRU_ACTIVE_ANON);
> > > -}
> > > -
> > > static inline void lru_cache_add_file(struct page *page)
> > > {
> > > __lru_cache_add(page, LRU_INACTIVE_FILE);
> > > }
> > >
> > > -static inline void lru_cache_add_active_file(struct page *page)
> > > -{
> > > - __lru_cache_add(page, LRU_ACTIVE_FILE);
> > > -}
> >
> > Did you intend to remove these two functions?
>
> This is for applying Hannes's commnet.
>
> > They do appear to be unused now, but they still make sense and might be
> > used in the future, perhaps.
>
> Personally, I don't like the strategy that anyone without me might
> use this function in the future. because It often never come.
>
> > It's OK to remove them, but I'm wondering
> > if it was deliberately included in this patch?
>
> Makes sense.
> OK, please drop current patch at once. I'll post V2.
Is OK, let's keep the change. I just wanted to check that it wasn't
made accidentally.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>,
Minchan Kim <minchan.kim@gmail.com>,
Hugh Dickins <hughd@google.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] tmpfs: Insert tmpfs cache pages to inactive list at first
Date: Fri, 21 May 2010 17:32:15 -0400 [thread overview]
Message-ID: <20100521173215.e2240f5b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100522085421.1E72.A69D9226@jp.fujitsu.com>
On Sat, 22 May 2010 09:04:30 +0900 (JST) KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> > > -static inline void lru_cache_add_active_anon(struct page *page)
> > > -{
> > > - __lru_cache_add(page, LRU_ACTIVE_ANON);
> > > -}
> > > -
> > > static inline void lru_cache_add_file(struct page *page)
> > > {
> > > __lru_cache_add(page, LRU_INACTIVE_FILE);
> > > }
> > >
> > > -static inline void lru_cache_add_active_file(struct page *page)
> > > -{
> > > - __lru_cache_add(page, LRU_ACTIVE_FILE);
> > > -}
> >
> > Did you intend to remove these two functions?
>
> This is for applying Hannes's commnet.
>
> > They do appear to be unused now, but they still make sense and might be
> > used in the future, perhaps.
>
> Personally, I don't like the strategy that anyone without me might
> use this function in the future. because It often never come.
>
> > It's OK to remove them, but I'm wondering
> > if it was deliberately included in this patch?
>
> Makes sense.
> OK, please drop current patch at once. I'll post V2.
Is OK, let's keep the change. I just wanted to check that it wasn't
made accidentally.
--
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:[~2010-05-22 0:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 8:44 [PATCH] tmpfs: Insert tmpfs cache pages to inactive list at first KOSAKI Motohiro
2010-05-19 8:44 ` KOSAKI Motohiro
2010-05-19 18:47 ` Rik van Riel
2010-05-19 18:47 ` Rik van Riel
2010-05-19 21:51 ` Johannes Weiner
2010-05-19 21:51 ` Johannes Weiner
2010-05-19 23:29 ` Minchan Kim
2010-05-19 23:29 ` Minchan Kim
2010-05-20 1:00 ` Wu Fengguang
2010-05-20 1:00 ` Wu Fengguang
2010-05-21 0:36 ` KOSAKI Motohiro
2010-05-21 0:36 ` KOSAKI Motohiro
2010-05-21 18:57 ` Andrew Morton
2010-05-21 18:57 ` Andrew Morton
2010-05-22 0:04 ` KOSAKI Motohiro
2010-05-22 0:04 ` KOSAKI Motohiro
2010-05-21 21:32 ` Andrew Morton [this message]
2010-05-21 21:32 ` Andrew Morton
2010-05-21 1:31 ` Hugh Dickins
2010-05-21 1:31 ` Hugh Dickins
2010-05-21 1:43 ` KOSAKI Motohiro
2010-05-21 1:43 ` KOSAKI Motohiro
2010-05-21 2:10 ` Hugh Dickins
2010-05-21 2:10 ` Hugh Dickins
2010-05-21 2:18 ` KOSAKI Motohiro
2010-05-21 2:18 ` KOSAKI Motohiro
2010-05-21 16:25 ` Henrique de Moraes Holschuh
2010-05-21 16:25 ` Henrique de Moraes Holschuh
2010-05-21 2:00 ` Rik van Riel
2010-05-21 2:00 ` Rik van Riel
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=20100521173215.e2240f5b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.com \
--cc=shaohua.li@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.