From: Tadeusz Struk <tadeusz.struk@intel.com>
To: David Miller <davem@davemloft.net>
Cc: ying.xue@windriver.com, herbert@gondor.apana.org.au, hch@lst.de,
viro@ZenIV.linux.org.uk, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: net: Remove iocb argument from sendmsg and recvmsg
Date: Wed, 11 Mar 2015 09:09:27 -0700 [thread overview]
Message-ID: <550068B7.8080403@intel.com> (raw)
In-Reply-To: <20150311.000248.417529352060472113.davem@davemloft.net>
On 03/10/2015 09:02 PM, David Miller wrote:
>
> Because of the way you quoted the patch, it looked like a list posting
> looping back to the list again, because of the "List-ID: " email header.
>
> Therefore your posting was blocked and you'll have to resend your posting
> in a way such that this doesn't happen.
>
Oops, sorry, here it is.
Hi,
After couple of attempts to implement an user space interface to crypto HW that would meet our performance requirements, and after discussion with Herbert, we have come to conclusion that using AF_ALG sockets and AIO interface is the way to go.
Unfortunately it looks like AIO operations will no longer be supported on sockets because of the commit 1b784140474e4fc94281a49e96c67d29df0efbde.
My question is why do we want to abandon AIO support in the socket layer? Is it not worth keeping it for scenarios like this?
Do we have any alternative?
Here is the mentioned patch.
https://patchwork.kernel.org/patch/5971491/
Regards,
Tadeusz
prev parent reply other threads:[~2015-03-11 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54FFAA5B.3080608@intel.com>
2015-03-11 3:18 ` net: Remove iocb argument from sendmsg and recvmsg Ying Xue
2015-03-11 3:25 ` Tadeusz Struk
2015-03-11 4:06 ` David Miller
2015-03-11 4:39 ` Tadeusz Struk
2015-03-11 4:06 ` David Miller
2015-03-11 16:25 ` Tadeusz Struk
2015-03-11 4:02 ` David Miller
2015-03-11 16:09 ` Tadeusz Struk [this message]
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=550068B7.8080403@intel.com \
--to=tadeusz.struk@intel.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=ying.xue@windriver.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;
as well as URLs for NNTP newsgroup(s).