From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 7/8] io: remove Error parameter from QIOTask thread worker
Date: Thu, 5 Jan 2017 16:09:47 -0600 [thread overview]
Message-ID: <857b8995-d924-e6a5-b453-e2fed1394b84@redhat.com> (raw)
In-Reply-To: <20170105160321.21786-8-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4138 bytes --]
On 01/05/2017 10:03 AM, Daniel P. Berrange wrote:
> Now that task objects have a directly associated error,
> there's no need for an an Error **errp parameter to
> the QIOTask thread worker function. It already has a
> QIOTask object, so can directly set the error on it.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> include/io/task.h | 19 +++++++++----------
> io/channel-socket.c | 47 ++++++++++++++++++++++-------------------------
> io/task.c | 10 +---------
> tests/test-io-task.c | 12 +++++-------
> 4 files changed, 37 insertions(+), 51 deletions(-)
>
> diff --git a/include/io/task.h b/include/io/task.h
> index 7b5bc43..dca57dc 100644
> --- a/include/io/task.h
> +++ b/include/io/task.h
> @@ -29,9 +29,8 @@ typedef struct QIOTask QIOTask;
> typedef void (*QIOTaskFunc)(QIOTask *task,
> gpointer opaque);
>
> -typedef int (*QIOTaskWorker)(QIOTask *task,
> - Error **errp,
> - gpointer opaque);
> +typedef void (*QIOTaskWorker)(QIOTask *task,
> + gpointer opaque);
Hmm, so you're getting rid of the return type here, because the QIOTask
now holds everything. I'm still not sure whether a void* return would be
easier, but I'm not going to reject your patch because of my bikeshedding.
>
> /**
> * QIOTask:
> @@ -163,18 +162,18 @@ typedef int (*QIOTaskWorker)(QIOTask *task,
> * socket listen using QIOTask would require:
> *
> * <example>
> - * static int myobject_listen_worker(QIOTask *task,
> - * Error **errp,
> - * gpointer opaque)
> + * static void myobject_listen_worker(QIOTask *task,
> + * gpointer opaque)
> * {
> * QMyObject obj = QMY_OBJECT(qio_task_get_source(task));
> * SocketAddress *addr = opaque;
> + * Error *err = NULL;
> *
> - * obj->fd = socket_listen(addr, errp);
> - * if (obj->fd < 0) {
> - * return -1;
> + * obj->fd = socket_listen(addr, &err);
> + *
> + * if (err) {
> + * qio_task_set_error(task, err);
I argued earlier that you can call this unconditionally, dropping the
'if (err)'. Both here in the doc example...
> +++ b/io/channel-socket.c
> @@ -156,19 +156,18 @@ int qio_channel_socket_connect_sync(QIOChannelSocket *ioc,
> }
>
>
> -static int qio_channel_socket_connect_worker(QIOTask *task,
> - Error **errp,
> - gpointer opaque)
> +static void qio_channel_socket_connect_worker(QIOTask *task,
> + gpointer opaque)
> {
> QIOChannelSocket *ioc = QIO_CHANNEL_SOCKET(qio_task_get_source(task));
> SocketAddress *addr = opaque;
> - int ret;
> + Error *err = NULL;
>
> - ret = qio_channel_socket_connect_sync(ioc,
> - addr,
> - errp);
> + qio_channel_socket_connect_sync(ioc, addr, &err);
>
> - return ret;
> + if (err) {
> + qio_task_set_error(task, err);
...and in the actual code. But I guess leaving it in doesn't hurt much,
either.
> @@ -107,10 +102,7 @@ static gpointer qio_task_thread_worker(gpointer opaque)
> struct QIOTaskThreadData *data = opaque;
>
> trace_qio_task_thread_run(data->task);
> - data->ret = data->worker(data->task, &data->err, data->opaque);
> - if (data->ret < 0 && data->err == NULL) {
> - error_setg(&data->err, "Task worker failed but did not set an error");
> - }
> + data->worker(data->task, data->opaque);
I like that your choice of making the error part of the QIOTask
simplifies the workers.
Up to you whether to simplify the conditionals.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-01-05 22:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:03 [Qemu-devel] [PATCH 0/8] io: enable DNS resolving separately of socket create Daniel P. Berrange
2017-01-05 16:03 ` [Qemu-devel] [PATCH 1/8] sockets: add ability to disable DNS resolution for InetSocketAddress Daniel P. Berrange
2017-01-05 16:22 ` Eric Blake
2017-01-05 16:42 ` Daniel P. Berrange
2017-01-05 16:03 ` [Qemu-devel] [PATCH 2/8] io: stop incrementing reference in qio_task_get_source Daniel P. Berrange
2017-01-05 16:30 ` Eric Blake
2017-01-05 16:03 ` [Qemu-devel] [PATCH 3/8] io: fix typo in docs for QIOTask Daniel P. Berrange
2017-01-05 20:29 ` Eric Blake
2017-01-05 16:03 ` [Qemu-devel] [PATCH 4/8] io: add ability to associate an opaque "result" with with a task Daniel P. Berrange
2017-01-05 20:32 ` Eric Blake
2017-01-06 9:14 ` Daniel P. Berrange
2017-01-05 16:03 ` [Qemu-devel] [PATCH 5/8] io: add ability to associate an error " Daniel P. Berrange
2017-01-05 21:03 ` Eric Blake
2017-01-06 9:16 ` Daniel P. Berrange
2017-01-05 16:03 ` [Qemu-devel] [PATCH 6/8] io: change the QIOTask callback signature Daniel P. Berrange
2017-01-05 21:47 ` Eric Blake
2017-01-06 12:05 ` Daniel P. Berrange
2017-01-05 16:03 ` [Qemu-devel] [PATCH 7/8] io: remove Error parameter from QIOTask thread worker Daniel P. Berrange
2017-01-05 22:09 ` Eric Blake [this message]
2017-01-05 16:03 ` [Qemu-devel] [PATCH 8/8] io: introduce a DNS resolver API Daniel P. Berrange
2017-01-05 22:51 ` Eric Blake
2017-01-06 12:19 ` Daniel P. Berrange
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=857b8995-d924-e6a5-b453-e2fed1394b84@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.