On Mon, Mar 23, 2015 at 02:13:21PM -0700, Tadeusz Struk wrote:
Herbert, is it possible to pull it to cryptodev?
How many more changes do you have that sit on top of this? If
it's small we could just push them through net-next until the
merge window opens again.
Cheers,
--
Email: Herbert Xu
From: Tadeusz Struk tadeusz.st...@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
On 03/23/2015 01:42 PM, David Miller wrote:
From: Tadeusz Struk tadeusz.st...@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
On Thu, Mar 19, 2015 at 07:51:05PM +, Al Viro wrote:
I think I can live with that. Christoph, do you have any objections to
that series?
Patch 1 looks fine to me which is probably what you care for. I didn't have
time to look into the other two.
--
To unsubscribe from this list: send the
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
On Thu, Mar 19, 2015 at 12:31:19PM -0700, Tadeusz Struk wrote:
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.
