All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Latency of Linux Bridge
Date: Fri, 22 Jul 2005 15:28:10 +0000	[thread overview]
Message-ID: <42E1108A.1020404@gmx.net> (raw)
In-Reply-To: <E0DE28DB991224419F668FC8DF59729A40042D@esealmw115.eemea.ericsson.se>

Hi,

Christian Konecny (VI/SEA) schrieb:
> I just recognized, that a basic bridge just with it's
> minumum configuration of 2 network interfaces creates
> latency of approx. 5ms on very low traffic.
> This seems to be independent on CPU speed. I tried on
> 2 GHz PC while having just 64kBit traffic with packet
> size of about 300bytes.

That's strange. On my bridge with 4 network interfaces,
the additional latency is always below 0.5 ms, even if
I'm pushing 400 MBit/s through the machine and a kernel
compile is running at 100% CPU. Network interfaces are
PCIe GBit from Syskonnect, the machine is an Athlon64
at 2 GHz. Even if the clock speed is halved by powersave
the additional latency will not go above 0.9 ms.
Kernel is vanilla 2.6.11.x.


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-07-22 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22  7:55 [LARTC] Latency of Linux Bridge Christian Konecny (VI/SEA)
2005-07-22  9:12 ` Jonathan Day
2005-07-22 11:35 ` Christian Konecny (VI/SEA)
2005-07-22 15:28 ` Carl-Daniel Hailfinger [this message]
2005-07-22 23:49 ` Stephen Hemminger
2005-07-26  7:15 ` Christian Konecny (VI/SEA)
2005-07-26 12:45 ` Carl-Daniel Hailfinger
2005-07-26 13:09 ` Christian Konecny (VI/SEA)
2005-07-26 14:37 ` Christian Konecny (VI/SEA)

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=42E1108A.1020404@gmx.net \
    --to=c-d.hailfinger.devel.2005@gmx.net \
    --cc=lartc@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.