[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00ac01c87656$777c02a0$667407e0$@com>
Date: Sat, 23 Feb 2008 11:58:30 -0800
From: "Hua Zhong" <hzhong@...il.com>
To: "'Andrew Morton'" <akpm@...ux-foundation.org>,
"'Andi Kleen'" <andi@...stfloor.org>
Cc: 'Ilpo Järvinen' <ilpo.jarvinen@...sinki.fi>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
"'David Miller'" <davem@...emloft.net>,
"'Arnaldo Carvalho de Melo'" <acme@...hat.com>
Subject: RE: [RFC PATCH 0/8]: uninline & uninline
> > Is there any reason they couldn't just be merged to mainline?
> >
> > I think it's a useful facility.
>
> ummm, now why did we made that decision... I think we decided that
> it's the sort of thing which one person can run once per few months
> and that will deliver its full value. I can maintain it in -mm and
> we're happy - no need to add it to mainline. No strong feelings
> either way really.
Apparently nobody has been doing it for a while. :-) Last time I did it it
was around the submission time and I actually patched it into mainline
kernel to do so. Not particularly hard to do, but sitting in mm-only does
make it a bit harder, and there are the vdso problem you just mentioned that
one has to fix for himself if it exists in mainline.
> It does have the downside that the kernel explodes if someone adds
> unlikely or likely to the vdso code and I need to occasionally hunt
> down new additions and revert them in that patch. That makes it a
> bit of a maintenance burden.
Is it possible to catch this automatically, like, by re-defining
likely/unlikely to the raw form in specific file(s)?
Hua
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists