From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
To: Jianyu Zhan <nasa4836@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
shli@kernel.org, bob.liu@oracle.com, sjenning@linux.vnet.ibm.com,
iamjoonsoo.kim@lge.com, aquini@redhat.com,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
khalid.aziz@oracle.com, LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/swap: cleanup *lru_cache_add* functions
Date: Mon, 21 Apr 2014 14:09:43 +0800 [thread overview]
Message-ID: <5354B627.2090201@cn.fujitsu.com> (raw)
In-Reply-To: <CAHz2CGWVo9ZXDY7S5_OU-6C1syiMuXX4qCpMUM+YCMkDUcSSZg@mail.gmail.com>
On 04/21/2014 12:02 PM, Jianyu Zhan wrote:
> Hi, Yanfei,
>
> On Mon, Apr 21, 2014 at 9:00 AM, Zhang Yanfei
> <zhangyanfei@cn.fujitsu.com> wrote:
>> What should be exported?
>>
>> lru_cache_add()
>> lru_cache_add_anon()
>> lru_cache_add_file()
>>
>> It seems you only export lru_cache_add_file() in the patch.
>
> Right, lru_cache_add_anon() is only used by VM code, so it should not
> be exported.
>
> lru_cache_add_file() and lru_cache_add() are supposed to be used by
> vfs ans fs code.
>
> But now only lru_cache_add_file() is used by CIFS and FUSE, which
> both could be
> built as module, so it must be exported; and lru_cache_add() has now
> no module users,
> so as Rik suggests, it is unexported too.
>
OK. So The sentence in the patch log confused me:
[ However, lru_cache_add() is supposed to
be used by vfs, or whatever others, but it is not exported.]
otherwise,
Reviewed-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Thanks.
--
Thanks.
Zhang Yanfei
--
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:[~2014-04-21 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 15:39 Jianyu Zhan
2014-04-18 21:14 ` Rik van Riel
2014-04-21 1:00 ` Zhang Yanfei
2014-04-21 4:02 ` Jianyu Zhan
2014-04-21 6:09 ` Zhang Yanfei [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-18 13:09 Jianyu Zhan
2014-04-18 13:51 ` Christoph Hellwig
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=5354B627.2090201@cn.fujitsu.com \
--to=zhangyanfei@cn.fujitsu.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=bob.liu@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=khalid.aziz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=nasa4836@gmail.com \
--cc=riel@redhat.com \
--cc=shli@kernel.org \
--cc=sjenning@linux.vnet.ibm.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