Subject: Re: 2.6.19 -mm merge plans (NTP changes)
From: john stultz <johnstul@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
In-Reply-To: <Pine.LNX.4.64.0609211217190.6761@scrub.home>
References: <20060920135438.d7dd362b.akpm@osdl.org>
	 <1158805731.8648.54.camel@localhost>
	 <Pine.LNX.4.64.0609211217190.6761@scrub.home>
Content-Type: text/plain
Date: Mon, 25 Sep 2006 09:50:04 -0700
Message-Id: <1159203005.8288.16.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1371
Lines: 33

On Thu, 2006-09-21 at 12:24 +0200, Roman Zippel wrote:
> Hi,
> 
> On Wed, 20 Sep 2006, john stultz wrote:
> 
> > No objections here, but I wanted to put forth some caution as I've seen
> > some odd NTP behavior with the full NTP patchset on my laptop (either it
> > does not converge or it just converges *much* more slowly then without).
> > Unfortunately I've not been able to collect solid enough data to analyze
> > the issue (really, each run should go for atleast a full day and always
> > run on the same network).
> 
> grumble...
> As I said before it's expected that the initial covergence is slower and I 
> need the data over multiple days to really say something about it.
> There has been really a lot of time for doing this...

Andrew, 
With apologies to Roman, I'm withdrawing my hesitation on these patches.
I was able to run tests for two days each w/ and w/o the patch I had
concerns about. And indeed, it seems if the drift file is reset, the
initial convergence is much slower (and this is really what worried me).
However once it converges it seems to keep sync as well as the current
code.

thanks
-john

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