From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>, boris.ostrovsky@oracle.com
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] pvcalls-front improvements
Date: Thu, 15 Feb 2018 18:28:47 +0100 [thread overview]
Message-ID: <320c6565-b003-ad4c-dcb0-f4eda4ed456f@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1802141023400.5392@sstabellini-ThinkPad-X260>
On 14/02/18 19:26, Stefano Stabellini wrote:
> Hi all,
>
> this small series introduces a per socket refcount to increase the
> efficiency on socket release operations, and makes releasing passive
> sockets safe.
>
> Cheers,
>
> Stefano
>
>
> Changes in v3:
> - remove pointless initializers
> - reorder pvcalls_enter_sock
>
> Changes in v2:
> - add acked-by
> - fix check in pvcalls_enter_soc
> - fix code style
> - nicer checks in pvcalls_front_release
>
>
> Stefano Stabellini (2):
> pvcalls-front: introduce a per sock_mapping refcount
> pvcalls-front: wait for other operations to return when release passive sockets
Both patches committed to xen/tip.git for-linus-4.16
Juergen
next prev parent reply other threads:[~2018-02-15 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 18:26 Stefano Stabellini
2018-02-14 18:28 ` [PATCH v3 1/2] pvcalls-front: introduce a per sock_mapping refcount Stefano Stabellini
2018-02-14 18:28 ` [PATCH v3 2/2] pvcalls-front: wait for other operations to return when release passive sockets Stefano Stabellini
2018-02-15 9:49 ` [PATCH v3 1/2] pvcalls-front: introduce a per sock_mapping refcount Juergen Gross
2018-02-15 17:28 ` Juergen Gross [this message]
2018-02-15 18:30 ` [PATCH v3 0/2] pvcalls-front improvements Stefano Stabellini
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=320c6565-b003-ad4c-dcb0-f4eda4ed456f@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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
all inboxes | Powered by JetHome®