From: Florian Weimer <fw@deneb.enyo.de>
To: "David S. Miller" <davem@redhat.com>
Cc: sim@netnation.org, linux-kernel@vger.kernel.org
Subject: Re: Route cache performance under stress
Date: Sun, 18 May 2003 11:21:14 +0200 [thread overview]
Message-ID: <87iss87gqd.fsf@deneb.enyo.de> (raw)
In-Reply-To: <20030517.150933.74723581.davem@redhat.com> (David S. Miller's message of "Sat, 17 May 2003 15:09:33 -0700 (PDT)")
"David S. Miller" <davem@redhat.com> writes:
> From: Florian Weimer <fw@deneb.enyo.de>
> Date: Sat, 17 May 2003 09:31:04 +0200
>
> The hash collision problem appears to be resolved, but not the more
> general performance issues. Or are there any kernels without a
> routing cache?
>
> I think your criticism of the routing cache is not well
> founded.
Well, what would change your mind?
I don't really care, as I maintain just one Linux router which routes
substantial bandwidth and which could easily be protected by upstream
ACLs in the case of an emergency. Others rely on Linux routers for
their ISP business, and they see similar problems as well, and these
people *do* care about this problem. Some of them contacted me and
told me that they were ignored when they described it. They certainly
want this problem to be fixed, as using FreeBSD is not always an
option. 8-(
next prev parent reply other threads:[~2003-05-18 9:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 16:37 Route cache performance under stress Florian Weimer
2003-04-05 18:17 ` Martin Josefsson
2003-04-05 18:34 ` Willy Tarreau
2003-05-16 22:24 ` Simon Kirby
2003-05-16 23:16 ` Florian Weimer
2003-05-19 19:10 ` Simon Kirby
2003-05-17 2:35 ` David S. Miller
2003-05-17 7:31 ` Florian Weimer
2003-05-17 22:09 ` David S. Miller
2003-05-18 9:21 ` Florian Weimer [this message]
2003-05-18 9:31 ` David S. Miller
2003-05-19 17:36 ` Jamal Hadi
2003-05-19 19:18 ` Ralph Doncaster
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 6:14 Scott A Crosby
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=87iss87gqd.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@netnation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox