public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] cryptoloop
Date: Thu, 3 Jul 2003 17:31:55 +0100	[thread overview]
Message-ID: <20030703173155.A10665@infradead.org> (raw)
In-Reply-To: <UTC200307031625.h63GPx209151.aeb@smtp.cwi.nl>; from Andries.Brouwer@cwi.nl on Thu, Jul 03, 2003 at 06:25:59PM +0200

On Thu, Jul 03, 2003 at 06:25:59PM +0200, Andries.Brouwer@cwi.nl wrote:
> They are used much more frequently than cryptoapi is.
> People tell me jari-loop is much faster at present.
> If this is true, your move would not be very popular.

Personally I care far less about one cryptoloop implementation
beeing faster than another one, but about proper design of whatever
gets into mainline. Think about this like the freeswan vs kernel
ipsec thing - of course klips had more feature and more mature code
initially (and maybe still has in some areas) but the kernel ipsec
is the much better design.

I'd be very interested in seeing some backing and explanation of his
claims so we can incorporate it into the generic cryptoapi / loop code.

The only thing I could imagine is that he has assembly implementations
of many ciphers that are faster than the C ones in cryptoapi - something
that's on the cryptoapi todo list anyway.

> Anyway, I am not doing a redesign. Just a cleanup.

Umm, no.  You add a feature.  That's something very different from
a cleanup.


  reply	other threads:[~2003-07-03 16:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 16:25 [PATCH] cryptoloop Andries.Brouwer
2003-07-03 16:31 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-04 13:21 Andries.Brouwer
2003-07-04 13:28 ` Christoph Hellwig
2003-07-04 11:08 Andries.Brouwer
2003-07-04 12:13 ` Christoph Hellwig
2003-07-02 22:57 Andries.Brouwer
2003-07-02 22:27 Andries.Brouwer
2003-07-02 21:00 Andries.Brouwer
2003-07-02 21:06 ` Greg KH
2003-07-02 21:31 ` Andrew Morton
2003-07-03 16:23 ` Christoph Hellwig
2003-07-02 19:42 Andries.Brouwer
2003-07-02 19:58 ` Andrew Morton
2003-07-02 18:44 Andries.Brouwer
2003-07-02 19:02 ` Andrew Morton
2003-07-02 19:16   ` Linus Torvalds
2003-07-02 19:20     ` Andrew Morton
2003-07-02 19:31       ` Linus Torvalds
2003-07-03 11:21 ` Jari Ruusu
2003-07-03 15:20   ` Andrew Morton
2003-07-03 17:29     ` Jari Ruusu
2003-07-03 17:38       ` Chris Friesen
2003-07-04  7:43         ` Jari Ruusu
2003-07-04  8:44           ` Andrew Morton
2003-07-04  9:41           ` Christoph Hellwig
2003-07-05  8:41             ` Jari Ruusu
2003-07-05  8:58               ` Andrew Morton
2003-07-05  9:00                 ` Andre Hedrick
2003-07-05  9:10               ` Andre Hedrick
2003-07-05 17:16               ` James Morris
2003-07-05 17:20               ` Linus Torvalds
2003-07-08 12:43               ` Christoph Hellwig
2003-07-04  9:39       ` Christoph Hellwig
2003-07-03 16:20 ` Christoph Hellwig
2003-07-02 15:21 Andries.Brouwer
2003-07-02 17:16 ` Andrew Morton
2003-07-03 15:44 ` Christoph Hellwig

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=20030703173155.A10665@infradead.org \
    --to=hch@infradead.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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