Re: [patch 00/46] High resolution timer / dynamic tick update

[Daniel Walker]

On Wed, 2007-01-24 at 08:07 +0100, Ingo Molnar wrote:
> * Daniel Walker <dwalker@xxxxxxxxxx> wrote:
> 
> > To lessen Andrews burden it would be wise to integrate the two trees 
> > prior to anything going into -mm .. [...]
> 
> i disagree. Thomas' tree has been tested in -rt for some time already, 
> and he's the author of this code so as far as i'm concerned he calls the 
> shots of what to do and in what order to do. He did the overwhelming 
> majority of regression fixes of dynticks/hrt stuff both in -mm and in 
> -rt. So why should i not take his queue over yours? Last i checked your 
> queue didnt really do anything substantial to the code - other than 
> shuffling around wast amounts of code around. Even this latest iteration 
> from Thomas that is now in -rt is working well on the target platform we 
> are aiming for currently (i686). (and it's working on x86_64 as well in 
> -rt)
> 
> 	Ingo

The majority of the new code was added yesterday in -rt8. Here is the
interdiff between -rt7 and -rt7

ftp://source.mvista.com/pub/dwalker/rt-interdiffs/patch-2.6.20-rc5-rt7-patch-2.6.20-rc5-rt8.patch

Since this new release has a fair amount of new code it's not totally
fair to says "it's been in -rt for a while".

My queue has always been 90% clean up, some of that is moving code
around. That's not all it does, and you can make an apples to apples
comparison between my tree and parts of this _new_ high res/dynamic tick
queue. 

If stability is a question, -rt10 does currently compile for my test
config, due to this new HRT introduction. I know from experience it's
going to take Thomas at least a few days just to make this new code
compile in all configs. This also means there are number of fairly
simple configs which this new HRT has not been tested in.

My patch set has been stable for months, and reviewed and tested by John
and I constantly (With you and Thomas on the CC list each release)..
It's a completely safe bet, IMO .

Daniel

-
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/