mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com,
	Stefano Stabellini <stefano@aporeto.com>
Subject: Re: [PATCH v3 11/18] xen/pvcalls: implement accept command
Date: Tue, 13 Jun 2017 09:24:41 +0200	[thread overview]
Message-ID: <c7d715eb-358a-47a7-95be-c87afc25c8b1@suse.com> (raw)
In-Reply-To: <1496431915-20774-11-git-send-email-sstabellini@kernel.org>

On 02/06/17 21:31, Stefano Stabellini wrote:
> Implement the accept command by calling inet_accept. To avoid blocking
> in the kernel, call inet_accept(O_NONBLOCK) from a workqueue, which get
> scheduled on sk_data_ready (for a passive socket, it means that there
> are connections to accept).
> 
> Use the reqcopy field to store the request. Accept the new socket from
> the delayed work function, create a new sock_mapping for it, map
> the indexes page and data ring, and reply to the other end. Allocate an
> ioworker for the socket.
> 
> Only support one outstanding blocking accept request for every socket at
> any time.
> 
> Add a field to sock_mapping to remember the passive socket from which an
> active socket was created.
> 
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> CC: boris.ostrovsky@oracle.com
> CC: jgross@suse.com
> ---
>  drivers/xen/pvcalls-back.c | 109 ++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 108 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
> index a75586e..f1173f4 100644
> --- a/drivers/xen/pvcalls-back.c
> +++ b/drivers/xen/pvcalls-back.c
> @@ -65,6 +65,7 @@ struct pvcalls_ioworker {
>  struct sock_mapping {
>  	struct list_head list;
>  	struct pvcalls_fedata *priv;
> +	struct sockpass_mapping *sockpass;
>  	struct socket *sock;
>  	uint64_t id;
>  	grant_ref_t ref;
> @@ -275,10 +276,79 @@ static int pvcalls_back_release(struct xenbus_device *dev,
>  
>  static void __pvcalls_back_accept(struct work_struct *work)
>  {
> +	struct sockpass_mapping *mappass = container_of(
> +		work, struct sockpass_mapping, register_work);
> +	struct sock_mapping *map;
> +	struct pvcalls_ioworker *iow;
> +	struct pvcalls_fedata *priv;
> +	struct socket *sock;
> +	struct xen_pvcalls_response *rsp;
> +	struct xen_pvcalls_request *req;
> +	int notify;
> +	int ret = -EINVAL;
> +	unsigned long flags;
> +
> +	priv = mappass->priv;
> +	/* We only need to check the value of "cmd" atomically on read. */
> +	spin_lock_irqsave(&mappass->copy_lock, flags);
> +	req = &mappass->reqcopy;
> +	if (req->cmd != PVCALLS_ACCEPT) {
> +		spin_unlock_irqrestore(&mappass->copy_lock, flags);
> +		return;
> +	}
> +	spin_unlock_irqrestore(&mappass->copy_lock, flags);

What about:
	req = &mappass->reqcopy;
	if (ACCESS_ONCE(req->cmd) != PVCALLS_ACCEPT)
		return;

I can't see the need for taking a lock here.

> +
> +	sock = sock_alloc();
> +	if (sock == NULL)
> +		goto out_error;
> +	sock->type = mappass->sock->type;
> +	sock->ops = mappass->sock->ops;
> +
> +	ret = inet_accept(mappass->sock, sock, O_NONBLOCK, true);
> +	if (ret == -EAGAIN) {
> +		sock_release(sock);
> +		goto out_error;
> +	}
> +
> +	map = pvcalls_new_active_socket(priv,
> +					req->u.accept.id_new,
> +					req->u.accept.ref,
> +					req->u.accept.evtchn,
> +					sock);
> +	if (!map) {
> +		sock_release(sock);
> +		goto out_error;
> +	}
> +
> +	map->sockpass = mappass;
> +	iow = &map->ioworker;
> +	atomic_inc(&map->read);
> +	atomic_inc(&map->io);
> +	queue_work_on(iow->cpu, iow->wq, &iow->register_work);
> +
> +out_error:
> +	rsp = RING_GET_RESPONSE(&priv->ring, priv->ring.rsp_prod_pvt++);
> +	rsp->req_id = req->req_id;
> +	rsp->cmd = req->cmd;
> +	rsp->u.accept.id = req->u.accept.id;
> +	rsp->ret = ret;
> +	RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&priv->ring, notify);
> +	if (notify)
> +		notify_remote_via_irq(priv->irq);
> +
> +	spin_lock_irqsave(&mappass->copy_lock, flags);
> +	mappass->reqcopy.cmd = 0;
> +	spin_unlock_irqrestore(&mappass->copy_lock, flags);

ACCESS_ONCE(mappass->reqcopy.cmd) = 0;

>  }
>  
>  static void pvcalls_pass_sk_data_ready(struct sock *sock)
>  {
> +	struct sockpass_mapping *mappass = sock->sk_user_data;
> +
> +	if (mappass == NULL)
> +		return;
> +
> +	queue_work(mappass->wq, &mappass->register_work);
>  }
>  
>  static int pvcalls_back_bind(struct xenbus_device *dev,
> @@ -380,7 +450,44 @@ static int pvcalls_back_listen(struct xenbus_device *dev,
>  static int pvcalls_back_accept(struct xenbus_device *dev,
>  			       struct xen_pvcalls_request *req)
>  {
> -	return 0;
> +	struct pvcalls_fedata *priv;
> +	struct sockpass_mapping *mappass;
> +	int ret = -EINVAL;
> +	struct xen_pvcalls_response *rsp;
> +	unsigned long flags;
> +
> +	priv = dev_get_drvdata(&dev->dev);
> +
> +	mappass = radix_tree_lookup(&priv->socketpass_mappings,
> +		req->u.accept.id);
> +	if (mappass == NULL)
> +		goto out_error;
> +
> +	/* 
> +	 * Limitation of the current implementation: only support one
> +	 * concurrent accept or poll call on one socket.
> +	 */
> +	spin_lock_irqsave(&mappass->copy_lock, flags);
> +	if (mappass->reqcopy.cmd != 0) {
> +		spin_unlock_irqrestore(&mappass->copy_lock, flags);
> +		ret = -EINTR;
> +		goto out_error;
> +	}
> +
> +	mappass->reqcopy = *req;

This time you need the lock, however you should use:

ACCESS_ONCE(mappass->reqcopy) = *req;

> +	spin_unlock_irqrestore(&mappass->copy_lock, flags);
> +	queue_work(mappass->wq, &mappass->register_work);
> +
> +	/* Tell the caller we don't need to send back a notification yet */
> +	return -1;
> +
> +out_error:
> +	rsp = RING_GET_RESPONSE(&priv->ring, priv->ring.rsp_prod_pvt++);
> +	rsp->req_id = req->req_id;
> +	rsp->cmd = req->cmd;
> +	rsp->u.accept.id = req->u.accept.id;
> +	rsp->ret = ret;
> +	return ret;

return 0?


Juergen

>  }
>  
>  static int pvcalls_back_poll(struct xenbus_device *dev,
> 

  reply	other threads:[~2017-06-13  7:25 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 19:31 [PATCH v3 00/18] introduce the Xen PV Calls backend Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-06-12 21:19     ` Boris Ostrovsky
2017-06-02 19:31   ` [PATCH v3 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-06-12 21:27     ` Boris Ostrovsky
2017-06-02 19:31   ` [PATCH v3 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini
2017-06-12 22:03     ` Boris Ostrovsky
2017-06-14 21:03       ` Stefano Stabellini
2017-06-15 14:33         ` Boris Ostrovsky
2017-06-15 18:54           ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-06-13  6:06     ` Juergen Gross
2017-06-14  0:46       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-06-13  6:17     ` Juergen Gross
2017-06-14  0:46       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 09/18] xen/pvcalls: implement bind command Stefano Stabellini
2017-06-13  7:00     ` Juergen Gross
2017-06-14  0:46       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-06-13  7:00     ` Juergen Gross
2017-06-02 19:31   ` [PATCH v3 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-06-13  7:24     ` Juergen Gross [this message]
2017-06-14  0:47       ` Stefano Stabellini
2017-06-14  6:32         ` Juergen Gross
2017-06-14 19:27           ` Stefano Stabellini
2017-06-15  6:58             ` Juergen Gross
2017-06-15 17:54               ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-06-13  7:28     ` Juergen Gross
2017-06-14  0:47       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-06-13  7:39     ` Juergen Gross
2017-06-14  0:47       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-06-13  7:49     ` Juergen Gross
2017-06-14  0:54       ` Stefano Stabellini
2017-06-14 13:51         ` Boris Ostrovsky
2017-06-14 19:15           ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini
2017-06-13  7:51     ` Juergen Gross
2017-06-14  0:56       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-06-13  7:56     ` Juergen Gross
2017-06-14  0:57       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-06-13  7:59     ` Juergen Gross
2017-06-14  1:00       ` Stefano Stabellini
2017-06-02 19:31   ` [PATCH v3 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini
2017-06-13  6:02     ` Juergen Gross
2017-06-13 23:46       ` Stefano Stabellini
2017-06-12 21:17   ` [PATCH v3 01/18] xen: introduce the pvcalls interface header Boris Ostrovsky

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=c7d715eb-358a-47a7-95be-c87afc25c8b1@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=stefano@aporeto.com \
    --cc=xen-devel@lists.xen.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®