From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: linux-crypto@vger.kernel.org,
Nico Erfurth <nico.erfurth@viprinet.com>,
Simon Kissel <simon.kissel@viprinet.com>
Subject: Re: RFC: kcrypto - (yet another) user space interface
Date: Fri, 11 Jun 2010 09:47:15 +0200 [thread overview]
Message-ID: <4C11EA03.50505@gnutls.org> (raw)
In-Reply-To: <20100610211433.GA25864@Chamillionaire.breakpoint.cc>
Sebastian Andrzej Siewior wrote:
> * Phil Sutter | 2010-06-10 20:22:29 [+0200]:
>
>> Hello everyone,
> Hi Phil,
>
> please take look at [0] and [1]. From README I can tell that those two
> posts are different from you have so far.
> You might want to take a look at AF_PACKET interface. It does zero copy
> via a ring buffer interface of pre-mmaped user memory. So no
> get_user_pages() then :)
>
> I think that is the way to go.
The problem with right or wrong is that they are only known afterwards.
For me the right way to go is _to go_. I can see discussions in this
least, years ago on talks about the "perfect" userspace crypto api and
rejections implementations because they are not perfect enough. I don't
believe there is such thing as a perfect crypto api. Other operating
systems have a userspace crypto API (maybe not perfect) but linux
hasn't. I don't think this is the way to go.
regards,
Nikos
next prev parent reply other threads:[~2010-06-11 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 18:22 RFC: kcrypto - (yet another) user space interface Phil Sutter
2010-06-10 21:14 ` Sebastian Andrzej Siewior
2010-06-11 7:47 ` Nikos Mavrogiannopoulos [this message]
2010-06-11 9:08 ` Sebastian Andrzej Siewior
2010-06-11 10:51 ` Phil Sutter
2010-06-11 17:00 ` Phil Sutter
2010-06-11 17:00 ` Phil Sutter
2010-06-12 16:40 ` Uri Simchoni
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=4C11EA03.50505@gnutls.org \
--to=nmav@gnutls.org \
--cc=linux-crypto@vger.kernel.org \
--cc=nico.erfurth@viprinet.com \
--cc=sebastian@breakpoint.cc \
--cc=simon.kissel@viprinet.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 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.