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 16/18] xen/pvcalls: implement read
Date: Tue, 13 Jun 2017 09:56:12 +0200	[thread overview]
Message-ID: <99664d75-df13-2e25-a992-0b8050776d49@suse.com> (raw)
In-Reply-To: <1496431915-20774-16-git-send-email-sstabellini@kernel.org>

On 02/06/17 21:31, Stefano Stabellini wrote:
> When an active socket has data available, increment the io and read
> counters, and schedule the ioworker.
> 
> Implement the read function by reading from the socket, writing the data
> to the data ring.
> 
> Set in_error on error.
> 
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> CC: boris.ostrovsky@oracle.com
> CC: jgross@suse.com
> ---
>  drivers/xen/pvcalls-back.c | 85 ++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 85 insertions(+)
> 
> diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
> index 0283d49..e7d2b85 100644
> --- a/drivers/xen/pvcalls-back.c
> +++ b/drivers/xen/pvcalls-back.c
> @@ -101,6 +101,81 @@ static int pvcalls_back_release_active(struct xenbus_device *dev,
>  
>  static void pvcalls_conn_back_read(unsigned long opaque)
>  {
> +	struct sock_mapping *map = (struct sock_mapping *)opaque;
> +	struct msghdr msg;
> +	struct kvec vec[2];
> +	RING_IDX cons, prod, size, wanted, array_size, masked_prod, masked_cons;
> +	int32_t error;
> +	struct pvcalls_data_intf *intf = map->ring;
> +	struct pvcalls_data *data = &map->data;
> +	unsigned long flags;
> +	int ret;
> +
> +	array_size = XEN_FLEX_RING_SIZE(map->ring_order);
> +	cons = intf->in_cons;
> +	prod = intf->in_prod;
> +	error = intf->in_error;
> +	/* read the indexes first, then deal with the data */
> +	virt_mb();
> +
> +	if (error)
> +		return;
> +
> +	size = pvcalls_queued(prod, cons, array_size);
> +	if (size >= array_size)
> +		return;
> +	spin_lock_irqsave(&map->sock->sk->sk_receive_queue.lock, flags);
> +	if (skb_queue_empty(&map->sock->sk->sk_receive_queue)) {
> +		atomic_set(&map->read, 0);
> +		spin_unlock_irqrestore(&map->sock->sk->sk_receive_queue.lock,
> +				flags);
> +		return;
> +	}
> +	spin_unlock_irqrestore(&map->sock->sk->sk_receive_queue.lock, flags);
> +	wanted = array_size - size;
> +	masked_prod = pvcalls_mask(prod, array_size);
> +	masked_cons = pvcalls_mask(cons, array_size);
> +
> +	memset(&msg, 0, sizeof(msg));
> +	msg.msg_iter.type = ITER_KVEC|WRITE;
> +	msg.msg_iter.count = wanted;
> +	if (masked_prod < masked_cons) {
> +		vec[0].iov_base = data->in + masked_prod;
> +		vec[0].iov_len = wanted;
> +		msg.msg_iter.kvec = vec;
> +		msg.msg_iter.nr_segs = 1;
> +	} else {
> +		vec[0].iov_base = data->in + masked_prod;
> +		vec[0].iov_len = array_size - masked_prod;
> +		vec[1].iov_base = data->in;
> +		vec[1].iov_len = wanted - vec[0].iov_len;
> +		msg.msg_iter.kvec = vec;
> +		msg.msg_iter.nr_segs = 2;
> +	}
> +
> +	atomic_set(&map->read, 0);
> +	ret = inet_recvmsg(map->sock, &msg, wanted, MSG_DONTWAIT);
> +	WARN_ON(ret > 0 && ret > wanted);

wanted is always > 0, so you can omit the ret > 0 test.


Juergen

> +	if (ret == -EAGAIN) /* shouldn't happen */
> +		return;
> +	if (!ret)
> +		ret = -ENOTCONN;
> +	spin_lock_irqsave(&map->sock->sk->sk_receive_queue.lock, flags);
> +	if (ret > 0 && !skb_queue_empty(&map->sock->sk->sk_receive_queue))
> +		atomic_inc(&map->read);
> +	spin_unlock_irqrestore(&map->sock->sk->sk_receive_queue.lock, flags);
> +
> +	/* write the data, then modify the indexes */
> +	virt_wmb();
> +	if (ret < 0)
> +		intf->in_error = ret;
> +	else
> +		intf->in_prod = prod + ret;
> +	/* update the indexes, then notify the other end */
> +	virt_wmb();
> +	notify_remote_via_irq(map->irq);
> +
> +	return;
>  }
>  
>  static int pvcalls_conn_back_write(struct sock_mapping *map)
> @@ -173,6 +248,16 @@ static void pvcalls_sk_state_change(struct sock *sock)
>  
>  static void pvcalls_sk_data_ready(struct sock *sock)
>  {
> +	struct sock_mapping *map = sock->sk_user_data;
> +	struct pvcalls_ioworker *iow;
> +
> +	if (map == NULL)
> +		return;
> +
> +	iow = &map->ioworker;
> +	atomic_inc(&map->read);
> +	atomic_inc(&map->io);
> +	queue_work_on(iow->cpu, iow->wq, &iow->register_work);
>  }
>  
>  static struct sock_mapping *pvcalls_new_active_socket(
> 

  reply	other threads:[~2017-06-13  7:56 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
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 [this message]
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=99664d75-df13-2e25-a992-0b8050776d49@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®