[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0705021346170.16517@blonde.wat.veritas.com>
Date: Wed, 2 May 2007 13:54:53 +0100 (BST)
From: Hugh Dickins <hugh@...itas.com>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Christoph Lameter <clameter@....com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: 2.6.22 -mm merge plans: slub
On Tue, 1 May 2007, Andrew Morton wrote:
>
> Given the current state and the current rate of development I'd expect slub
> to have reached the level of completion which you're describing around -rc2
> or -rc3. I think we'd be pretty safe making that assumption.
Its developer does show signs of being active!
>
> This is a bit unusual but there is of course some self-interest here: the
> patch dependencies are getting awful and having this hanging around
> out-of-tree will make 2.6.23 development harder for everyone.
That is a very strong argument: a somewhat worrisome argument,
but a very strong one. Maintaining your sanity is important.
>
> So on balance, given that we _do_ expect slub to have a future, I'm
> inclined to crash ahead with it. The worst that can happen will be a later
> rm mm/slub.c which would be pretty simple to do.
Okay. And there's been no chorus to echo my concern.
But if Linus' tree is to be better than a warehouse to avoid
awkward merges, I still think we want it to default to on for
all the architectures, and for most if not all -rcs.
>
> otoh I could do some frantic patch mangling and make it easier to carry
> slub out-of-tree, but do we gain much from that?
No, keep away from that.
Hugh
-
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