mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Sightler <ttsig@tuxyturvy.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: jmorris@intercode.com.au, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Poor IPSec performance with 2.6 kernels
Date: 28 Aug 2003 09:09:23 -0400	[thread overview]
Message-ID: <1062076162.1907.21.camel@iso-8590-lx.zeusinc.com> (raw)
In-Reply-To: <200308281016.h7SAGKi24571@freya.yggdrasil.com>


> 	In which direction did you take these benchmarks, inbound to the
> Linux box, outbound from the Linux box, or both?  If both, is
> there a difference between inbound and outbound performance?  What
> private key algorithm are you configuring (aes, des, serpent)?  How
> is your DSL connected (via ethernet, via USB, such as with SpeedStream)?
> What kind of CPU are you using (probably doesn't matter, even if you're
> using a 16MHz 386, but it would help in reproducing your problem to
> know what the benchmarks should look like on a different system).

Unfortunately my DSL service is ADSL and my uplink is only 256Kbps which
gives me about 25-30KB/s on a typical, non-IPsec FTP upload.  Both SFS
and in-kernel IPsec give approximately the same outbound speed over this
limited link, roughly 20KB/s, which seems about right to me.

I'm using 3des for the encryption algorithm.

DSL is connected via ethernet.

CPU is an AMD K6/2 333Mhz.

I also just thought about the fact that I could test my laptop to see if
this is a CPU related issue.  It's running the same basic kernel but of
course with options for laptop devices enabled and compiled for i686,
etc.  It's a much faster machine, a PIII/1.13Ghz system.  If I still get
roughly the same performance then we can probably safely assume it's not
a CPU constraint.  I'll test the tonight.

I'm also going to try and pull some TCP dump data to see if it gives me
any hints.

Anything else I can answer.

Later,
Tom




  reply	other threads:[~2003-08-28 13:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 10:16 Adam J. Richter
2003-08-28 13:09 ` Tom Sightler [this message]
2003-08-28 13:40   ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2003-09-01 17:25 kartikey bhatt
2003-08-30 17:13 kartikey bhatt
2003-08-28 18:56 kartikey bhatt
2003-08-29  1:37 ` James Morris
2003-08-28  2:38 Tom Sightler
2003-08-28  2:56 ` James Morris

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=1062076162.1907.21.camel@iso-8590-lx.zeusinc.com \
    --to=ttsig@tuxyturvy.com \
    --cc=adam@yggdrasil.com \
    --cc=jmorris@intercode.com.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®