From: Glen Turner <glen.turner@aarnet.edu.au>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: netdev@oss.sgi.com
Subject: Re: Linux Routing Performance Update
Date: Sat, 29 Jan 2005 00:26:40 +1030 [thread overview]
Message-ID: <41FA4498.6020202@aarnet.edu.au> (raw)
In-Reply-To: <16887.39598.648724.421160@robur.slu.se>
> Finally time for some more testing with a somewhat upgraded equipment.
Thanks very much for the interesting results.
I'm sure other network engineers have experienced software routers where
the pps has dramatically slowed down upon reasonable ACLs and queuing
(Cisco 7500, etc), so some results with netfilter and tc running would
be appreciated, as would tests for any packet re-ordering in output flows.
[ For a reasonable ACL, Team Crymu's list of aggregated Bogon addresses
is a representative choice. For a basic QoS, consider three queues:
control, VoIP, data. With an approximation to fair queuing + RED on
the data queue. ]
Best wishes,
Glen
next prev parent reply other threads:[~2005-01-28 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 13:27 Linux Routing Performance Update Robert Olsson
2005-01-28 13:56 ` Glen Turner [this message]
2005-01-29 18:50 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2005-01-29 22:21 Guthrie, Jeremy
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=41FA4498.6020202@aarnet.edu.au \
--to=glen.turner@aarnet.edu.au \
--cc=Robert.Olsson@data.slu.se \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).