From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Loc Ho <lho@amcc.com>
Cc: linux-crypto@vger.kernel.org, Shasi Pulijala <spulijala@amcc.com>
Subject: Re: OpenSSL patch to support Linux CryptoAPI.
Date: Sat, 9 Aug 2008 10:29:41 +0400 [thread overview]
Message-ID: <20080809062941.GA25828@2ka.mipt.ru> (raw)
In-Reply-To: <0CA0A16855646F4FA96D25A158E299D604D28FD5@SDCEXCHANGE01.ad.amcc.com>
Hi.
On Fri, Aug 08, 2008 at 03:24:20PM -0700, Loc Ho (lho@amcc.com) wrote:
> This sound like the only solution to passing more than one pointers from user space is via custom system call - such as (new) crypto_op(...). Am I correct?
No, it is not a right solution. Linux has so ugly compat layer to fix
this problems, that it is much better not to look at it before the
dinner.
You do not need to pass multiple pointers, but instead a multiple data.
You can do that via single area provided to the kernel and multiple size
fields, where each one corresponds to the size of the contiguous sectors
in the provided data.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-08-09 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 18:31 OpenSSL patch to support Linux CryptoAPI Shasi Pulijala
2008-08-08 21:09 ` Evgeniy Polyakov
2008-08-08 22:24 ` Loc Ho
2008-08-09 6:29 ` Evgeniy Polyakov [this message]
2008-08-11 18:53 ` Loc Ho
2008-08-11 19:53 ` Evgeniy Polyakov
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=20080809062941.GA25828@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=lho@amcc.com \
--cc=linux-crypto@vger.kernel.org \
--cc=spulijala@amcc.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