From: Al Viro <viro@ZenIV.linux.org.uk>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: davem@davemloft.net, linux-aio@kvack.org,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
ying.xue@windriver.com, bcrl@kvack.org,
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: Thu, 19 Mar 2015 19:51:05 +0000 [thread overview]
Message-ID: <20150319195105.GS29656@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20150319193118.11500.10463.stgit@tstruk-mobl1>
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.
>
> 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
I think I can live with that. Christoph, do you have any objections to
that series?
next prev parent reply other threads:[~2015-03-19 19:51 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 ` Al Viro [this message]
2015-03-20 6:45 ` [PATCH v3 net-next 0/3] Add support for async socket operations Christoph Hellwig
2015-03-23 20:42 ` David Miller
2015-03-23 21:13 ` Tadeusz Struk
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=20150319195105.GS29656@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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=tadeusz.struk@intel.com \
--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 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.