From: Dave Dillow <dave@thedillows.org>
To: Miika Komu <miika@iki.fi>
Cc: Patrick McHardy <kaber@trash.net>, Netdev <netdev@oss.sgi.com>
Subject: Re: IPsec performance
Date: Tue, 03 May 2005 01:54:38 -0400 [thread overview]
Message-ID: <1115099678.2953.3.camel@ori.thedillows.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0505030820160.24686@kekkonen.cs.hut.fi>
On Tue, 2005-05-03 at 08:25 +0300, Miika Komu wrote:
> However, this does explain why I got only 1.9 megabytes/s with 3DES.
What was your hardware? Without knowing what you're running on, it's
impossible to tell if that is good or bad.
Linux Journal was getting ~5.5MB/s on a PIV 2.2GHz.
I get ~2.1MB/s on a 550MHz Athlon.
Dave
next prev parent reply other threads:[~2005-05-03 5:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 18:39 IPsec performance Miika Komu
2005-05-02 19:09 ` Miika Komu
2005-05-03 0:55 ` Patrick McHardy
2005-05-03 5:25 ` Miika Komu
2005-05-03 5:54 ` Dave Dillow [this message]
2005-05-03 6:44 ` Miika Komu
2005-05-03 14:17 ` Dave Dillow
2005-05-03 16:14 ` Miika Komu
2005-05-03 19:27 ` Dave Dillow
2005-05-03 19:27 ` David S. Miller
2005-05-04 11:34 ` jamal
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 21:09 ipsec performance Andreas Schuldei
2009-12-29 22:55 ` Abhijit Karmarkar
2009-12-29 23:31 ` Andreas Schuldei
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=1115099678.2953.3.camel@ori.thedillows.org \
--to=dave@thedillows.org \
--cc=kaber@trash.net \
--cc=miika@iki.fi \
--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).