From: "David S. Miller" <davem@redhat.com>
To: skraw@ithnet.com
Cc: ahu@ds9a.nl, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH] USAGI IPsec
Date: Sat, 12 Oct 2002 22:42:12 -0700 (PDT) [thread overview]
Message-ID: <20021012.224212.56861427.davem@redhat.com> (raw)
In-Reply-To: <20021012140644.0d403b2c.skraw@ithnet.com>
From: Stephan von Krawczynski <skraw@ithnet.com>
Date: Sat, 12 Oct 2002 14:06:44 +0200
This was a 2.2.19 kernel with equal-cost-multipath enabled
and large routing-tables enabled.
It doesn't surprise me that 2.2.x performs like crap under
any real load btw :-) It has none of the 2.3.x scalability
and threading work.
next prev parent reply other threads:[~2002-10-13 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3u1js1l1a.wl@karaba.org>
[not found] ` <20021011.185332.115906289.davem@redhat.com>
2002-10-12 2:43 ` [PATCH] USAGI IPsec YOSHIFUJI Hideaki / 吉藤英明
2002-10-12 2:41 ` David S. Miller
2002-10-12 11:17 ` bert hubert
2002-10-12 11:41 ` David S. Miller
2002-10-12 12:06 ` Stephan von Krawczynski
2002-10-13 5:42 ` David S. Miller [this message]
2002-10-12 12:16 ` bert hubert
2002-10-13 5:43 ` David S. Miller
2002-10-11 8:05 Mitsuru KANDA
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=20021012.224212.56861427.davem@redhat.com \
--to=davem@redhat.com \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=skraw@ithnet.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).