mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ivan Kalatchev" <ivan.kalatchev@esg.ca>
To: <linux-kernel@vger.kernel.org>
Subject: System time slowdown after upgrading from 2.4 to 2.6
Date: Thu, 19 Aug 2004 15:42:41 -0400	[thread overview]
Message-ID: <000501c48624$b1ac72f0$2e646434@ivans> (raw)

Hi all,

We have a project that uses PC-104 (ZFx86 100 MHz CPU) Linux box to acquire
some seismological signals. System resides on a M-Systems DiskOnChip 2000.
We have an ISA acquisition card that acquires data into FIFO buffer and
triggers interrupt as soon as 341 points were acquired (then this data is
read out in interrupt handler routine). System worked perfectly well when we
used 2.4.18 kernel. When I printk-ed system time (do_gettimeofday)  in
interrupt routine, at 1kHz sampling frequency interrupts were reported every
341 msec as they should do.
But after I've switched to 2.6 kernel (2.6.7 - preempted, then I tried
2.6.8 - non-preempted) time between successive interrupts at 1kHz became 335
msec, losing 6 msec at each interrupt. What is interesting, when sampling
frequency is 10 kHz, with 2.4.18 kernel interrupts are reported every 34
msec, which is right, but with 2.6 kernels interrupts are coming at 28 msec
interval, again losing same 6 msec!

Any ideas why this might happen?

Please, CC me all answers/comments posted to the list in response to this
posting.
Regards,

Ivan Kalatchev

Senior Software Developer
Engineering Seismology Group Canada Inc.
ISO 9001-2000
1 Hyperion Court, Kingston,
Ontarion, Canada K7K 7G3
phone: (613) 548-8287 ext.247
fax:     (613) 548-8917



             reply	other threads:[~2004-08-19 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 19:42 Ivan Kalatchev [this message]
2004-08-19 20:58 ` john stultz
2004-08-19 21:14 ` Tim Schmielau

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='000501c48624$b1ac72f0$2e646434@ivans' \
    --to=ivan.kalatchev@esg.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®