All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: "Egi, Norbert" <n.egi@lancaster.ac.uk>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Performance loss with bridging+routing.
Date: Sat, 07 Apr 2007 16:16:19 +0200	[thread overview]
Message-ID: <1175955379.2974.9.camel@localhost.localdomain> (raw)
In-Reply-To: <BB501CE635E5144CA5E30956E5E32C52271F0F@exchange-be5.lancs.local>

Op do, 15-03-2007 te 17:59 +0000, schreef Egi, Norbert:
> Sorry, it looks like the spaces have different sizes in my mailing
> system. I hope the graphs are more readable now.

The performance drop comes from the fact that your routed traffic is
buffered twice. The first time before the bridge code gets its hands on
it, the second time when the bridge code decides the packet is destined
for the bridge itself and sends it back to the buffer. I've at times
wondered if it were feasible and acceptable to get rid of this second
buffering... At first glance it seems quite feasible, but maybe it would
cause performance trouble elsewhere. Dunno...
You can probably circumvent the performance drop using the ebtables
brouting chain. See
http://ebtables.sourceforge.net/examples/example2.html

cheers,
Bart

PS: try to make your mailer cut lines @ 78 characters when sending
messages to Linux lists



      parent reply	other threads:[~2007-04-07 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 17:05 [Bridge] Performance loss with bridging+routing Egi, Norbert
2007-03-15 17:59 ` Egi, Norbert
2007-03-17 16:11   ` Jason Lunz
2007-03-19 18:27     ` Stephen Hemminger
2007-03-20  9:40       ` Egi, Norbert
2007-04-07 14:16   ` Bart De Schuymer [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=1175955379.2974.9.camel@localhost.localdomain \
    --to=bdschuym@pandora.be \
    --cc=bridge@lists.osdl.org \
    --cc=n.egi@lancaster.ac.uk \
    /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.