mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark_H_Johnson@raytheon.com
To: Ingo Molnar <mingo@elte.hu>
Cc: Karsten Wiese <annabellesgarden@yahoo.de>,
	Bill Huey <bhuey@lnxw.com>, Adam Heath <doogie@debian.org>,
	"K.R. Foley" <kr@cybsft.com>,
	linux-kernel@vger.kernel.org,
	Florian Schmidt <mista.tapas@gmx.net>,
	Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	Lee Revell <rlrevell@joe-job.com>,
	Rui Nuno Capela <rncbc@rncbc.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.1
Date: Thu, 4 Nov 2004 09:02:01 -0600	[thread overview]
Message-ID: <OF4142E065.5AF4099C-ON86256F42.00513CF0@raytheon.com> (raw)

Let me follow up briefly on the regression I noticed yesterday on ping
responses from an SMP system with one real time task running. Two systems
were used for the tests, both dual 866 Mhz Pentium III systems, identical
except for the software. The "old" machine is running Red Hat 7.3 with a
2.4.24 preempt, low latency kernel. The "new" machine is running Fedora
Core 2 with a 2.6 kernel as indicated below. The other difference that may
be significant is the "old" system uses OSS and the new one uses ALSA for
the audio output (source of latencytest application is unchanged for all
three tests).

The data below is from using another machine to ping the system under test.

2.4.24 preempt + low latency on "old" machine

430 seconds for the complete series of tests
0 lost packets
0.248, 0.322, 2.82, 0.145 (min, average, max, deviation)

2.6.5-1.358smp [from fedora core 2] on "new" machine

658 seconds for the complete series of tests
0 lost packets
0.148, 0.207, 1.952, 0.097 (min, average, max, deviation)
This system also lost the mouse (screaming interrupts, IRQ 10 disabled).

2.6.9-rc3-mm3-VP-T3 on "new machine"

955 seconds for the complete series of tests
539 lost packets
0.215, 17971, 287799, 63054 (min, average, max, deviation)

I did not repeat the tests on -V0.7.7, but I expect them to come out
similar to -T3 above based on what I saw yesterday. In any case, the loss
of network data appears significant with both the voluntary preempt &
realtime preempt patches on 2.6 kernels.

--Mark H Johnson
  <mailto:Mark_H_Johnson@raytheon.com>


             reply	other threads:[~2004-11-04 15:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 15:02 Mark_H_Johnson [this message]
2004-11-04 15:16 ` Ingo Molnar
2004-11-04 15:19   ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2004-11-04 19:39 Mark_H_Johnson
2004-11-04 19:52 ` Ingo Molnar
2004-11-04 17:52 Mark_H_Johnson
2004-11-04 16:53 Mark_H_Johnson
2004-11-04 16:22 Mark_H_Johnson
2004-11-04 16:30 ` Ingo Molnar
2004-11-04 16:32   ` Ingo Molnar
2004-11-04 18:59     ` john cooper
2004-11-04 19:44       ` Ingo Molnar
2004-11-04 23:25         ` john cooper
2004-11-05 21:42         ` Scott Wood
2004-11-05 22:36           ` Bill Huey
2004-11-08 14:35             ` Esben Nielsen
2004-11-08 15:42               ` Ingo Molnar
2004-11-08 22:47               ` Bill Huey
2004-11-06  7:42           ` Ingo Molnar
2004-11-04 16:04 Mark_H_Johnson
2004-11-04 16:13 ` Ingo Molnar
2004-11-04 16:17 ` Ingo Molnar
2004-11-03 20:40 Mark_H_Johnson
2004-11-03 18:24 Mark_H_Johnson
2004-10-18 14:50 [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U5 Ingo Molnar
2004-10-19 12:46 ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U6 Ingo Molnar
2004-10-19 18:00   ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U7 Ingo Molnar
2004-10-20  9:45     ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U8 Ingo Molnar
2004-10-21 13:27       ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U9 Ingo Molnar
2004-10-22 13:35         ` [patch] Real-Time Preemption, -RT-2.6.9-rc4-mm1-U9.3 Ingo Molnar
2004-10-22 15:50           ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-U10 Ingo Molnar
2004-10-22 17:56             ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-U10.2 Ingo Molnar
2004-10-25 10:40               ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0 Ingo Molnar
2004-10-27  0:15                 ` [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.3 Ingo Molnar
2004-11-03 10:58                   ` [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.1 Ingo Molnar
2004-11-03 13:44                     ` Lorenzo Allegrucci
2004-11-03 13:46                       ` Ingo Molnar
2004-11-03 17:53                         ` Lorenzo Allegrucci
2004-11-03 20:41                           ` Lorenzo Allegrucci
2004-11-03 20:43                             ` Ingo Molnar
2004-11-03 21:05                               ` Lorenzo Allegrucci
2004-11-03 19:33                     ` john cooper
2004-11-03 23:03                     ` Magnus Naeslund(t)
2004-11-04  6:56                       ` Ingo Molnar
2004-11-04 19:34                     ` Gunther Persoons
2004-11-04 20:31                       ` Chris Friesen

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=OF4142E065.5AF4099C-ON86256F42.00513CF0@raytheon.com \
    --to=mark_h_johnson@raytheon.com \
    --cc=annabellesgarden@yahoo.de \
    --cc=bhuey@lnxw.com \
    --cc=doogie@debian.org \
    --cc=kr@cybsft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mista.tapas@gmx.net \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rlrevell@joe-job.com \
    --cc=rncbc@rncbc.org \
    --cc=tglx@linutronix.de \
    --cc=xschmi00@stud.feec.vutbr.cz \
    /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®