All of lore.kernel.org
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 w/ GPS time source: worse performance
Date: Wed, 18 Oct 2006 18:44:59 +0200	[thread overview]
Message-ID: <45365A0B.5030306@xs4all.nl> (raw)
In-Reply-To: <1161189384.15860.85.camel@mindpipe>

Lee Revell wrote:
> On Wed, 2006-10-18 at 17:20 +0200, Udo van den Heuvel wrote:
>> Lee Revell wrote:
>>> On Tue, 2006-10-17 at 17:25 +0200, Udo van den Heuvel wrote:
>>>> Why does a GPS as time source (with ntpd) perform so much worse with 2.6.18?
>>> Um... you don't give nearly enough information to even begin to know
>>> what you're talking about.
>> No one here with a vague idea about the cause for the bad performance?
>> I am sure I not the only one experiencing this.
> 
> No, the issue is that a one-sentence bug report is not helpful.  You
> don't give enough information to debug it.  Kernel config, steps to
> reproduce, etc, etc.
> 
> Please look at LKML archives for some examples of the type of bug report
> that does get a response.

Get the latest kernel.
Compile for your system
Get ntpd.
Configure for your PPS/NMEA source.
Run ntpd.
Watch performance.
Repeat watching of performance.

It is not a crash. Not an oops.
It is stuff that is visible by watching ntpq -pn output, by letting mrtg
graph stuff, etc. Watch the offset and jitter collumns.
Check /usr/sbin/ntpdc -c kerninfo output. Graph that stuff.
Over the monhts you see changes. Some of them you can explain. Some you
can't.

I can understand this is not you everyday bug but this *is* an issue.


  reply	other threads:[~2006-10-18 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 15:25 2.6.18 w/ GPS time source: worse performance Udo van den Heuvel
2006-10-17 16:46 ` Lee Revell
2006-10-17 17:07   ` Udo van den Heuvel
2006-10-18 15:20   ` Udo van den Heuvel
2006-10-18 16:36     ` Lee Revell
2006-10-18 16:44       ` Udo van den Heuvel [this message]
2006-10-18 19:57         ` Valdis.Kletnieks
2006-10-18 21:46           ` Lee Revell
2006-10-18 23:17             ` john stultz
2006-10-19 14:12               ` Udo van den Heuvel
2006-10-19 14:14           ` Udo van den Heuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45365A0B.5030306@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.