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 15/18] xen/pvcalls: implement the ioworker functions
Date: Tue, 13 Jun 2017 09:51:39 +0200	[thread overview]
Message-ID: <51e3bbad-d5f2-a3b9-b038-4535cd58ea2a@suse.com> (raw)
In-Reply-To: <1496431915-20774-15-git-send-email-sstabellini@kernel.org>

On 02/06/17 21:31, Stefano Stabellini wrote:
> We have one ioworker per socket. Each ioworker goes through the list of
> outstanding read/write requests. Once all requests have been dealt with,
> it returns.
> 
> We use one atomic counter per socket for "read" operations and one
> for "write" operations to keep track of the reads/writes to do.
> 
> We also use one atomic counter ("io") per ioworker to keep track of how
> many outstanding requests we have in total assigned to the ioworker. The
> ioworker finishes when there are none.
> 
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> CC: boris.ostrovsky@oracle.com
> CC: jgross@suse.com
> ---
>  drivers/xen/pvcalls-back.c | 27 +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
> 
> diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
> index 6afe7a0..0283d49 100644
> --- a/drivers/xen/pvcalls-back.c
> +++ b/drivers/xen/pvcalls-back.c
> @@ -99,8 +99,35 @@ static int pvcalls_back_release_active(struct xenbus_device *dev,
>  				       struct pvcalls_fedata *priv,
>  				       struct sock_mapping *map);
>  
> +static void pvcalls_conn_back_read(unsigned long opaque)

Why not void *opaque? You could drop the cast below then.


Juergen

> +{
> +}
> +
> +static int pvcalls_conn_back_write(struct sock_mapping *map)
> +{
> +	return 0;
> +}
> +
>  static void pvcalls_back_ioworker(struct work_struct *work)
>  {
> +	struct pvcalls_ioworker *ioworker = container_of(work,
> +		struct pvcalls_ioworker, register_work);
> +	struct sock_mapping *map = container_of(ioworker, struct sock_mapping,
> +		ioworker);
> +
> +	while (atomic_read(&map->io) > 0) {
> +		if (atomic_read(&map->release) > 0) {
> +			atomic_set(&map->release, 0);
> +			return;
> +		}
> +
> +		if (atomic_read(&map->read) > 0)
> +			pvcalls_conn_back_read((unsigned long)map);
> +		if (atomic_read(&map->write) > 0)
> +			pvcalls_conn_back_write(map);
> +
> +		atomic_dec(&map->io);
> +	}
>  }
>  
>  static int pvcalls_back_socket(struct xenbus_device *dev,
> 

  reply	other threads:[~2017-06-13  7:51 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 [this message]
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=51e3bbad-d5f2-a3b9-b038-4535cd58ea2a@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

Powered by JetHome