From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org, Mel Gorman <mgorman@suse.de>,
linux-mm@kvack.org, Dave Hansen <dave.hansen@intel.com>
Subject: Re: [RFC] mm: show message when updating min_free_kbytes in thp
Date: Fri, 10 Jan 2014 00:13:44 -0800 [thread overview]
Message-ID: <20140110001344.2af08f11.akpm@linux-foundation.org> (raw)
In-Reply-To: <20140110080504.GA9437@dhcp22.suse.cz>
On Fri, 10 Jan 2014 09:05:04 +0100 Michal Hocko <mhocko@suse.cz> wrote:
> > > --- a/mm/huge_memory.c
> > > +++ b/mm/huge_memory.c
> > > @@ -100,6 +100,7 @@ static struct khugepaged_scan khugepaged_scan = {
> > > .mm_head = LIST_HEAD_INIT(khugepaged_scan.mm_head),
> > > };
> > >
> > > +extern int user_min_free_kbytes;
> > >
> >
> > We don't add extern declarations to .c files. How many other examples of
> > this can you find in mm/?
>
> I have suggested this because general visibility is not needed.
It's best to use a common declaration which is seen by the definition
site and all references, so everyone agrees on the variable's type.
Otherwise we could have "long foo;" in one file and "extern char foo;"
in another and the compiler won't tell us. I think the linker could
tell us, but it doesn't, afaik. Perhaps there's an option...
> But if
> you think that it should then include/linux/mm.h sounds like a proper
> place.
mm/internal.h might suit.
--
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-01-10 8:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 0:29 [RFC] mm: show message when updating min_free_kbytes in thp Han Pingtian
2014-01-02 18:05 ` Dave Hansen
2014-01-02 21:58 ` David Rientjes
2014-01-02 22:10 ` Dave Hansen
2014-01-02 23:36 ` David Rientjes
2014-01-02 23:48 ` Dave Hansen
2014-01-03 3:33 ` Han Pingtian
2014-01-03 18:17 ` Dave Hansen
2014-01-05 0:35 ` Han Pingtian
2014-01-06 16:46 ` Michal Hocko
2014-01-08 3:59 ` Han Pingtian
2014-01-08 8:20 ` Han Pingtian
2014-01-08 10:16 ` Michal Hocko
2014-01-09 7:32 ` Han Pingtian
2014-01-09 9:02 ` Michal Hocko
2014-01-09 21:15 ` David Rientjes
2014-01-10 8:05 ` Michal Hocko
2014-01-10 8:13 ` Andrew Morton [this message]
2014-01-10 8:17 ` Michal Hocko
2014-01-11 3:27 ` Han Pingtian
2014-01-14 20:07 ` Han Pingtian
2014-01-14 23:52 ` Andrew Morton
2014-01-15 0:25 ` David Rientjes
2014-01-15 0:35 ` Andrew Morton
2014-01-15 0:52 ` David Rientjes
2014-01-15 15:22 ` Mel Gorman
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=20140110001344.2af08f11.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).