From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Jean-Michel Hautbois <jhautbois@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Real time issues when using a bridge
Date: Tue, 12 Oct 2010 10:10:51 -0700 [thread overview]
Message-ID: <20101012101051.43dfd499@nehalam> (raw)
In-Reply-To: <AANLkTin=6Uf_fwGWJ9Q6CQct1cARtHWHJ0geNRz0JDed@mail.gmail.com>
On Tue, 12 Oct 2010 16:31:36 +0200
Jean-Michel Hautbois <jhautbois@gmail.com> wrote:
> Hi there !
>
> I am facing a jitter issue that I will try to explain :
> I have the following configuration :
>
> (A) eth0 <--> br0 <--> eth1 (B)
>
> I have a small and custom kernel (I removed netfilter, for instance) and I
> am measuring the time between A and B (using hardware taps, etc.).
> My bandwidth is quite small (each packet is about 200 bytes and there is a
> delay of 10ms between each packet).
> I am measuring both the latency and the jitter (max_latency - min_latency)
> and this one is quite large.
>
> I added ftrace option, and after some (long) investigations, I am currently
> limiting my study to the bridge part.
>
> When I trace only br_handle_frame and br_forward_finish and do my test on
> 6500 frames I have :
> - average latency of 39µs
> - minimum latency of 34 µs
> - maximum latency of 81µs
>
> Thus, my jitter is 47µs.
> This may seem low, but this is about two to three times what I expect and I
> cannot see why a bridge which is only forwarding a frame would have jitter ?
> If you have any idea, everything is interesting for me.
> I thought maybe to skb_clone ?
>
> Best Regards,
> JM
You probably have NAPI and/or interrupt coalescing setting
enabled on one or both of the devices.
--
next prev parent reply other threads:[~2010-10-12 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 14:31 [Bridge] Real time issues when using a bridge Jean-Michel Hautbois
2010-10-12 17:10 ` Stephen Hemminger [this message]
2010-10-13 6:40 ` Jean-Michel Hautbois
2010-10-13 6:44 ` Jean-Michel Hautbois
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=20101012101051.43dfd499@nehalam \
--to=shemminger@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=jhautbois@gmail.com \
/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.