From: Michael Olbrich <m.olbrich@pengutronix.de>
To: linux-rt-users@vger.kernel.org
Cc: Robert Schwebel <r.schwebel@pengutronix.de>, kiszka@rts.uni-hannover.de
Subject: Re: jitter bursts
Date: Wed, 5 Sep 2007 10:14:02 +0200 [thread overview]
Message-ID: <20070905081402.GA30955@pengutronix.de> (raw)
In-Reply-To: <34ac6d890708310855v413383cm2bd725501a685842@mail.gmail.com>
On Fri, Aug 31, 2007 at 09:25:08PM +0530, Girish kathalagiri wrote:
> We also had similar problems when where we face these kind of periodic
> jitter. In our case we used Intel 82551ER Fast Ethernet Controller(
> e100 driver ). The problem with ours was the with the microcode (in
> e100.c) of the adapter which had default algorithm where the hardware
> was holding of the interrupts until X packets or Y usecs have expired.
>
> This generated a periodic jitter that was 400-500 us more than the usual one.
> This was solved by making the hardware generate interrupt on every frame.
> In e100.c this can be done by changing the values of INTDELAY,
> BUNDDLEMAX and BUNDDLESMALL (CPU saver parameters)
Unfortunately not but it did get me on the right track. The problem is
caused by the e100_watchdog function. As far as I can tell e100_watchdog
is called from a timer queue and therefore runs with the priority of
that thread. And while I set higher priorities for softirq-net-rx and
the application I missed the thread for the hardware interrupt of the
network interface. So whenever a packet arived while e100_watchdog was
running it got delayed. The periodic pattern is a result of this and
speed difference of sender and receiver clocks.
The jitter is now <50us but still with some periodic patterns. So I'll
need to investigate further.
michael
--
Pengutronix - Linux Solutions for Science and Industry
Entwicklungszentrum Nord http://www.pengutronix.de
next prev parent reply other threads:[~2007-09-05 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 15:17 jitter bursts Robert Schwebel
2007-08-31 15:55 ` Girish kathalagiri
2007-09-01 9:15 ` Robert Schwebel
2007-09-05 8:14 ` Michael Olbrich [this message]
2007-09-05 8:36 ` Girish kathalagiri
2007-09-05 9:01 ` Michael Olbrich
2007-08-31 15:58 ` Bernhard Kuhn
2007-09-01 9:13 ` Robert Schwebel
2007-08-31 16:55 ` Sven-Thorsten Dietrich
2007-09-02 12:05 ` Robert Schwebel
[not found] ` <46D92C57.3090703@osadl.org>
2007-09-01 9:19 ` jitter bursts -> Not Found Robert Schwebel
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=20070905081402.GA30955@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=kiszka@rts.uni-hannover.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
/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.