Re: [patch] voluntary-preempt-2.6.8-rc3-O4

[Lee Revell]

On Tue, 2004-08-10 at 03:51, Ingo Molnar wrote:
> * Lee Revell <rlrevell@xxxxxxxxxxx> wrote:
> 
> > Ingo, do you plan to maintain the voluntary preempt patch against the
> > -mm series?  From looking at Andrew's announcement yesterday it looks
> > like many latency issues fixed in the voluntary preemption patches are
> > also fixed in -mm, so it seems like the patch would be much smaller. 
> 
> yeah, and in addition we've already pushed 99% of our might_sleep()
> additions to -mm too so that reduces the patch size too, quite
> significantly.
> 
> time is the only limiting factor. Due to these partial merges (we are
> trying to get all uncontroversial bits into -mm, hence into upstream)
> the merge to -mm is hard. Especially for lock-breaks that i've done
> differently than Andrew. I sent a consolidation patch yesterday but this
> is still work in progress. So i'll do an -mm merge very time i get to do
> it, but the primary testing still remains on the vanilla kernel (which
> most people use).
> 

Rather than having to maintain the voluntary preempt patch for the -mm
series, after the next -mm merge, maybe you could just post or send me
an incremental diff against the last voluntary preempt patch for the
vanilla kernel when you update it, and I or someone else from the Linux
audio community could maintain the patch against the -mm series.  It
seems that lately the changes from one version of the patch to the next
are small and easy enough to comprehend.  We could also filter the bug
reports a bit.  Maybe a voluntary preemption mailing list is in order,
if this gets to be a constant source of huge log postings to LKML.

This would also improve the ability of the Linux audio community to
influence the direction of the kernel, by separately analyzing the
impact of different changes, especially if the -mm series is going to
function as 2.7 for the time being.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/