All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: linux-kernel@vger.kernel.org
Subject: [OT]AMD/Intel interrupt latency (jitter) differences?
Date: Fri, 25 Oct 2002 15:40:45 -0400	[thread overview]
Message-ID: <3DB99E3D.798B9A5F@compro.net> (raw)

 We have a proprietary application that is an emulation of an old real-time os
(MPX-32). We have a couple of pieces of hardware (pci cards) with soon to be GPL
drivers that go along with the emulation package and the hardware. We are using
a 2.4.18 kernel with the O(1) scheduler and a couple of other patches. One of
these pieces of hardware is a pci card with 6 each 1us resolution timers and 8
external interrupts (4 in and 4 out). We have fortran a program on the old
real-time os that tells us about the interrupt latency and determinism (jitter).
When we run this program in the emulation on an intel box all is well. When we
run this in the emulation on an AMD MP 1900+ box the determinism (jitter) is
very bad. Sometimes as much as 500us. On the Dual Intel 2.2 p4 zeon the
determinism (jitter) is under 50us. All the other benchmarks we run under the
emulation tell us that the AMD box is the faster box. It's also cheaper. So I
guess my question is, are there any known problem with AMD's and interrupt
latency jitter. I might also add that the only way we get satisfactory numbers,
even on the P4 zeons, was with the affinity calls in the O(1) scheduler along
with the affinitization of the pci cards' irq. We basically create a pset for
our app using these affinity calls then do the same with the irqs down in the
driver for this pci card. So our emulation is run in one processor and all else
(linux) in the other. We do the same for all the irqs. Why does this only give
good results on intel and not amd??? We have tested many intel MB/P4 combos but
only one AMD, a Tyan s2466n.

Sorry if I'm wasting your time
Thanks and regards

Mark

             reply	other threads:[~2002-10-25 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 19:40 Mark Hounschell [this message]
2002-10-25 19:56 ` [OT]AMD/Intel interrupt latency (jitter) differences? Richard B. Johnson
2002-10-25 20:45   ` Mark Hounschell
2002-10-25 21:08     ` Alan Cox
2002-10-25 20:35 ` Alan Cox
2002-10-25 20:43   ` Mark Hounschell

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=3DB99E3D.798B9A5F@compro.net \
    --to=markh@compro.net \
    --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.