public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Cc: linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com,
	Stefano Stabellini <stefano@aporeto.com>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Ron Minnich <rminnich@sandia.gov>,
	Latchesar Ionkov <lucho@ionkov.net>,
	v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH v3 6/7] xen/9pfs: receive responses
Date: Tue, 14 Mar 2017 08:04:06 +0100	[thread overview]
Message-ID: <5a0e3642-5eb4-e192-7241-39cf78a89fbd@suse.com> (raw)
In-Reply-To: <1489449019-13343-6-git-send-email-sstabellini@kernel.org>

On 14/03/17 00:50, Stefano Stabellini wrote:
> Upon receiving a notification from the backend, schedule the
> p9_xen_response work_struct. p9_xen_response checks if any responses are
> available, if so, it reads them one by one, calling p9_client_cb to send
> them up to the 9p layer (p9_client_cb completes the request). Handle the
> ring following the Xen 9pfs specification.
> 
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> CC: jgross@suse.com
> CC: Eric Van Hensbergen <ericvh@gmail.com>
> CC: Ron Minnich <rminnich@sandia.gov>
> CC: Latchesar Ionkov <lucho@ionkov.net>
> CC: v9fs-developer@lists.sourceforge.net
> ---
>  net/9p/trans_xen.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 55 insertions(+)
> 
> diff --git a/net/9p/trans_xen.c b/net/9p/trans_xen.c
> index b40bbcb..1a7eb52 100644
> --- a/net/9p/trans_xen.c
> +++ b/net/9p/trans_xen.c
> @@ -168,6 +168,61 @@ static int p9_xen_request(struct p9_client *client, struct p9_req_t *p9_req)
>  
>  static void p9_xen_response(struct work_struct *work)
>  {
> +	struct xen_9pfs_front_priv *priv;
> +	struct xen_9pfs_dataring *ring;
> +	RING_IDX cons, prod, masked_cons, masked_prod;
> +	struct xen_9pfs_header h;
> +	struct p9_req_t *req;
> +	int status;
> +
> +	ring = container_of(work, struct xen_9pfs_dataring, work);
> +	priv = ring->priv;
> +
> +	while (1) {
> +		cons = ring->intf->in_cons;
> +		prod = ring->intf->in_prod;
> +		virt_rmb();
> +
> +		if (xen_9pfs_queued(prod, cons, XEN_9PFS_RING_SIZE) < sizeof(h)) {
> +			notify_remote_via_irq(ring->irq);
> +			return;
> +		}
> +
> +		masked_prod = xen_9pfs_mask(prod, XEN_9PFS_RING_SIZE);
> +		masked_cons = xen_9pfs_mask(cons, XEN_9PFS_RING_SIZE);
> +
> +		/* First, read just the header */
> +		xen_9pfs_read_packet(ring->data.in,
> +				masked_prod, &masked_cons,
> +				XEN_9PFS_RING_SIZE, &h, sizeof(h));
> +
> +		req = p9_tag_lookup(priv->client, h.tag);
> +		if (!req || req->status != REQ_STATUS_SENT) {
> +			dev_warn(&priv->dev->dev, "Wrong req tag=%x\n", h.tag);
> +			cons += h.size;
> +			virt_mb();
> +			ring->intf->in_cons = cons;
> +			continue;
> +		}
> +
> +		memcpy(req->rc, &h, sizeof(h));
> +		req->rc->offset = 0;
> +
> +		masked_cons = xen_9pfs_mask(cons, XEN_9PFS_RING_SIZE);
> +		/* Then, read the whole packet (including the header) */
> +		xen_9pfs_read_packet(ring->data.in,
> +				masked_prod, &masked_cons,
> +				XEN_9PFS_RING_SIZE, req->rc->sdata, h.size);

Please align the parameters to the same column.

> +
> +		virt_mb();
> +		cons += h.size;
> +		ring->intf->in_cons = cons;
> +
> +		status = (req->status != REQ_STATUS_ERROR) ?
> +			REQ_STATUS_RCVD : REQ_STATUS_ERROR;
> +
> +		p9_client_cb(priv->client, req, status);
> +	}
>  }
>  
>  static irqreturn_t xen_9pfs_front_event_handler(int irq, void *r)
> 


Juergen

  reply	other threads:[~2017-03-14  7:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 23:50 [PATCH v3 0/7] Xen transport for 9pfs frontend driver Stefano Stabellini
2017-03-13 23:50 ` [PATCH v3 1/7] xen: import new ring macros in ring.h Stefano Stabellini
2017-03-13 23:50   ` [PATCH v3 2/7] xen: introduce the header file for the Xen 9pfs transport protocol Stefano Stabellini
2017-03-13 23:50   ` [PATCH v3 3/7] xen/9pfs: introduce Xen 9pfs transport driver Stefano Stabellini
2017-03-14  6:24     ` Juergen Gross
2017-03-14 20:26       ` Stefano Stabellini
2017-03-13 23:50   ` [PATCH v3 4/7] xen/9pfs: connect to the backend Stefano Stabellini
2017-03-14  6:41     ` Juergen Gross
2017-03-14 21:22       ` Stefano Stabellini
2017-03-15  5:08         ` Juergen Gross
2017-03-15 18:44           ` Stefano Stabellini
2017-03-16  5:54             ` Juergen Gross
2017-03-16 18:03               ` Stefano Stabellini
2017-03-17  4:54                 ` Juergen Gross
2017-03-17 15:13                   ` [Xen-devel] " Konrad Rzeszutek Wilk
2017-03-17 20:55                     ` Stefano Stabellini
2017-03-13 23:50   ` [PATCH v3 5/7] xen/9pfs: send requests " Stefano Stabellini
2017-03-13 23:50   ` [PATCH v3 6/7] xen/9pfs: receive responses Stefano Stabellini
2017-03-14  7:04     ` Juergen Gross [this message]
2017-03-14 20:32       ` Stefano Stabellini
2017-03-13 23:50   ` [PATCH v3 7/7] xen/9pfs: build 9pfs Xen transport driver Stefano Stabellini
2017-03-14  7:05     ` Juergen Gross
2017-03-15 16:30 ` [PATCH v3 0/7] Xen transport for 9pfs frontend driver Greg Kurz
2017-03-15 19:12   ` 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=5a0e3642-5eb4-e192-7241-39cf78a89fbd@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=rminnich@sandia.gov \
    --cc=sstabellini@kernel.org \
    --cc=stefano@aporeto.com \
    --cc=v9fs-developer@lists.sourceforge.net \
    --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