From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: jeremy@goop.org, jaswinderrajput@gmail.com,
randy.dunlap@oracle.com, linux-kernel@vger.kernel.org,
x86@kernel.org, righi.andrea@gmail.com
Subject: Re: mmotm 2009-02-02-17-12 uploaded (x86/nopmd etc.)
Date: Tue, 3 Feb 2009 13:41:28 -0800 [thread overview]
Message-ID: <20090203134128.37042ea8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090203212538.GB20527@elte.hu>
On Tue, 3 Feb 2009 22:25:38 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Tue, 3 Feb 2009 20:18:04 +0100
> > Ingo Molnar <mingo@elte.hu> wrote:
> >
> > >
> > > * Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > >
> > > > akpm@linux-foundation.org wrote:
> > > > > The mm-of-the-moment snapshot 2009-02-02-17-12 has been uploaded to
> > > > >
> > > > > http://userweb.kernel.org/~akpm/mmotm/
> > > > >
> > > > > and will soon be available at
> > > > >
> > > > > git://git.zen-sources.org/zen/mmotm.git
> > > >
> > > >
> > > > There seems to be some kind of #include hell here. I moved a few lines
> > > > around in include/asm-generic/pgtable-nopmd.h & that makes the build
> > > > get further, but it still has header problems (BUG() is undefined).
> > >
> > > problem caused by which commit?
> > >
> >
> > mm-unify-some-pmd_-functions-and-move-them-in-a-distinct-include.patch
> >
> > This is getting painful.
>
> the include file spaghetti is ... interesting there, and it's historic.
>
> I could blame it on highmem, PAE or paravirt - but i'll only blame it on
> paravirt for now because those developers are still around! ;-)
>
> Jeremy, any ideas how to reduce the historic dependency mess in that area?
> I think we should go on three routes at once:
>
> - agressive splitup and separation of type definitions from method
> declaration (+ inline definitions). The spinlock_types.h / spinlock.h
> splitup was really nice in solving such dependency problems.
I like this one. The mixing up of declare-something with use-something
is often the source of our woes.
> - uninlining of methods: instead of macro-ing them - wherever possible.
> It's really hard to mess up type + externs headers - while headers with
> inlines and macros mixed in get painful quickly.
>
> - removal of spurious pile of dozens of #include lines in header files.
>
> If anyone sends such patches i could try them on the -tip build machinery
> and help shake out collateral damage - which there will be for sure.
>
> Ingo
next prev parent reply other threads:[~2009-02-03 21:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200902030112.n131CNiq010549@imap1.linux-foundation.org>
2009-02-03 18:58 ` mmotm 2009-02-02-17-12 uploaded (x86/nopmd etc.) Randy Dunlap
2009-02-03 19:18 ` Ingo Molnar
2009-02-03 20:17 ` Andrew Morton
2009-02-03 21:25 ` Ingo Molnar
2009-02-03 21:41 ` Andrew Morton [this message]
2009-02-04 20:08 ` Ingo Molnar
2009-02-04 21:25 ` Andrew Morton
2009-02-04 21:29 ` Ingo Molnar
2009-02-04 21:32 ` Andrea Righi
2009-02-03 22:37 ` Jeremy Fitzhardinge
2009-02-04 19:56 ` Ingo Molnar
2009-02-03 22:13 ` [PATCH] sunrpc: fix rdma dependencies Randy Dunlap
2009-02-03 23:20 ` David Miller
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=20090203134128.37042ea8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jaswinderrajput@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=righi.andrea@gmail.com \
--cc=x86@kernel.org \
/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