|| ||Andrew Morton <akpm-AT-osdl.org>|
|| ||Re: [ckrm-tech] [RFC] [PATCH 00/12] CKRM after a major overhaul|
|| ||Fri, 21 Apr 2006 15:57:27 -0700|
|| ||haveblue-AT-us.ibm.com, linux-kernel-AT-vger.kernel.org,
Chandra Seetharaman <firstname.lastname@example.org> wrote:
> On Fri, 2006-04-21 at 07:49 -0700, Dave Hansen wrote:
> > On Thu, 2006-04-20 at 19:24 -0700, email@example.com wrote:
> > > CKRM has gone through a major overhaul by removing some of the complexity,
> > > cutting down on features and moving portions to userspace.
> > What do you want done with these patches? Do you think they are ready
> > for mainline? -mm? Or, are you just posting here for comments?
> We think it is ready for -mm. But, want to go through a review cycle in
> lkml before i request Andrew for that.
From a quick scan, the overall code quality is probably the best I've seen
for an initial submission of this magnitude. I had a few minor issues and
questions, but it'd need a couple of hours to go through it all.
So. Send 'em over when you're ready.
I have one concern. If we merge this framework into mainline then we'd
(quite reasonably) expect to see an ongoing dribble of new controllers
being submitted. But we haven't seen those controllers yet. So there is a
risk that you'll submit a major new controller (most likely a net or memory
controller) and it will provoke a reviewer revolt. We'd then be in a
situation of cant-go-forward, cant-go-backward.
It would increase the comfort level if we could see what the major
controllers look like before committing. But that's unreasonable.
Could I ask that you briefly enumerate
a) which controllers you think we'll need in the forseeable future
b) what they need to do
c) pointer to prototype code if poss
to post comments)