All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT]AMD/Intel interrupt latency (jitter) differences?
Date: Fri, 25 Oct 2002 16:43:28 -0400	[thread overview]
Message-ID: <3DB9ACF0.A7DBA5C4@compro.net> (raw)
In-Reply-To: 1035578152.13244.44.camel@irongate.swansea.linux.org.uk

Alan Cox wrote:
> 
> On Fri, 2002-10-25 at 20:40, Mark Hounschell wrote:
> > 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,
> 
> A lot of the IRQ delivery depends on the APIC. SO for example you'd
> probably see horrible numbers on a PIII, but very good on PIV. It also
> depends on chipset vagueries. You might also need to check that your PCI
> behaviour has no posting errors since the AMD certainly seems to do a
> lot more aggressive PCI posting.
> 
> Does "noapic" change the jitter ?

Actually if I use noapci then the irq affinity stuff does not work, which in
itself causes
the jitter to be unexceptable. On the AMD, the process and irq affinity appears
to be working
correctly, according to /proc/interrupts, but maybe it's really not??? Thats
what it acts
like. It acts just like if I hadn't set the affinity for the emulation and irq
on the P4,
just not as bad.

Regards
Mark

      reply	other threads:[~2002-10-25 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 19:40 [OT]AMD/Intel interrupt latency (jitter) differences? Mark Hounschell
2002-10-25 19:56 ` 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 [this message]

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=3DB9ACF0.A7DBA5C4@compro.net \
    --to=markh@compro.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.