From: Tadeusz Struk <tadeusz.struk@intel.com>
To: David Miller <davem@davemloft.net>
Cc: linux-aio@kvack.org, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, ying.xue@windriver.com, bcrl@kvack.org,
viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
hch@lst.de, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/3] Add support for async socket operations
Date: Mon, 23 Mar 2015 14:13:21 -0700 [thread overview]
Message-ID: <551081F1.9090303@intel.com> (raw)
In-Reply-To: <20150323.164221.1726829049738525120.davem@davemloft.net>
On 03/23/2015 01:42 PM, David Miller wrote:
> From: Tadeusz Struk <tadeusz.struk@intel.com>
> Date: Thu, 19 Mar 2015 12:31:19 -0700
>
>> After the iocb parameter has been removed from sendmsg() and recvmsg() ops
>> the socket layer, and the network stack no longer support async operations.
>> This patch set adds support for asynchronous operations on sockets back.
>>
>> Changes in v3:
>> * As sugested by Al Viro instead of adding new functions aio_sendmsg
>> and aio_recvmsg, added a ptr to iocb into the kernel-side msghdr structure.
>> This way no change to aio.c is required.
>>
>> Changes in v2:
>> * removed redundant total_size param from aio_sendmsg and aio_recvmsg functions
>
> Series applied to net-next.
>
Thanks Dave!
Herbert, is it possible to pull it to cryptodev?
next prev parent reply other threads:[~2015-03-23 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 19:31 [PATCH v3 net-next 0/3] Add support for async socket operations Tadeusz Struk
2015-03-19 19:31 ` [PATCH v3 net-next 1/3] net: socket: add support for async operations Tadeusz Struk
2015-03-19 19:31 ` [PATCH v3 net-next 2/3] crypto: af_alg - Allow to link sgl Tadeusz Struk
2015-03-19 19:31 ` [PATCH v3 net-next 3/3] crypto: algif - change algif_skcipher to be asynchronous Tadeusz Struk
2015-03-19 19:51 ` [PATCH v3 net-next 0/3] Add support for async socket operations Al Viro
2015-03-20 6:45 ` Christoph Hellwig
2015-03-23 20:42 ` David Miller
2015-03-23 21:13 ` Tadeusz Struk [this message]
2015-03-24 11:29 ` Herbert Xu
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=551081F1.9090303@intel.com \
--to=tadeusz.struk@intel.com \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-aio@kvack.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@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).