All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>, linux-crypto@vger.kernel.org
Subject: Re: [RFC] [PATCH 2/5] pcrypt: Add pcrypt crypto parallelization wrapper
Date: Tue, 23 Jun 2009 11:14:29 +0200	[thread overview]
Message-ID: <20090623091429.GC20366@secunet.com> (raw)
In-Reply-To: <20090623083438.GA8315@gondor.apana.org.au>

On Tue, Jun 23, 2009 at 04:34:38PM +0800, Herbert Xu wrote:
> On Tue, Jun 23, 2009 at 10:29:21AM +0200, Steffen Klassert wrote:
> >
> > I did already tests with a work queue based parallelization, but the
> > throughput and the latency on networking tests were much better with the
> > remote softirq based version. The serialization engine must always wait
> > for the cpu that processes the 'next' packet to keep the packets in the
> > right order. And softirqs are a good way to ensure that the packets are
> > processed as soon as possible.
> 
> OK, do you have some numbers that we can add to the patches?

I posted some numbers for the actual softirq based version with the
first patchset, see:
http://www.mail-archive.com/linux-crypto@vger.kernel.org/msg03035.html

But as I pointed out there, these numbers are not that meaningful
as long as we have the lock in crypto_authenc_hash()
Actually I'm about to rewrite authenc/hmac to use ahash. As soon as I
finished this I will redo the tests without the lock.

> 
> Also note that the real time folks are turning softirq into threads
> so this complexity might be moot in the end.
> 

Yes, I know. The one of the main problems of the thread based version
was that it had to wait for the cpu that serves the interrupt for the
NICs. As soon as other softirqs (like the NET_RX_SOFTIRQ) are thread
based too this should not be a problem any more.

  reply	other threads:[~2009-06-23  9:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  7:07 [RFC] [PATCH 0/5] Parallel IPsec v4 Steffen Klassert
2009-06-08  7:08 ` [RFC] [PATCH 1/5] padata: generic interface for parallel processing Steffen Klassert
2009-06-08  7:10 ` [RFC] [PATCH 2/5] pcrypt: Add pcrypt crypto parallelization wrapper Steffen Klassert
2009-06-19 12:21   ` Herbert Xu
2009-06-23  6:21     ` Steffen Klassert
2009-06-19 12:29   ` Herbert Xu
2009-06-23  8:29     ` Steffen Klassert
2009-06-23  8:34       ` Herbert Xu
2009-06-23  9:14         ` Steffen Klassert [this message]
2009-06-23  9:18           ` Herbert Xu
2009-06-23 10:19             ` Steffen Klassert
2009-06-23 10:19               ` Herbert Xu
2009-06-08  7:10 ` [RFC] [PATCH 3/5] eseqiv: Add support for aead algorithms Steffen Klassert
2009-06-25 10:46   ` Herbert Xu
2009-06-29 11:12     ` Steffen Klassert
2009-06-08  7:11 ` [RFC] [PATCH 4/5] authenc: Check if the IV is already added to the scatterlist Steffen Klassert
2009-06-08  7:12 ` [RFC] [PATCH 5/5] tcrypt: Test algorithms by name Steffen Klassert
2009-06-19 10:53   ` Herbert Xu
2009-06-19 10:56     ` Herbert Xu
2009-06-19 11:40       ` [PATCH] " Steffen Klassert
2009-06-19 11:47         ` Herbert Xu
2009-06-19 12:38           ` Herbert Xu
2009-06-23  6:04             ` Steffen Klassert

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=20090623091429.GC20366@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.