From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: "Stefan Hajnoczi" <stefanha@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-block@nongnu.org, Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, John Snow <jsnow@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [RFC PATCH v2 04/25] include/block/block: split header into I/O and global state API
Date: Fri, 8 Oct 2021 09:26:20 +0200 [thread overview]
Message-ID: <7b37f097-8f91-d8c2-f813-a0ce896da2d8@redhat.com> (raw)
In-Reply-To: <YV7vwBNSWTQGXOB6@stefanha-x1.localdomain>
On 07/10/2021 15:01, Stefan Hajnoczi wrote:
> On Thu, Oct 07, 2021 at 12:43:43PM +0100, Daniel P. Berrangé wrote:
>> On Tue, Oct 05, 2021 at 10:31:54AM -0400, Emanuele Giuseppe Esposito wrote:
>>> Similarly to the previous patch, split block.h
>>> in block-io.h and block-global-state.h
>>>
>>> block-common.h contains the structures shared between
>>> the two headers, and the functions that can't be categorized as
>>> I/O or global state.
>>
>> This is nice from a code organization POV, but it doesn't do all
>> that much from a code reviewer / author POV as I doubt anyone
>> will remember which header file the respective APIs/structures/
>> constants are in, without having to look it up each time.
Another thing to consider is with regards the function pointers API
split I do in patches 19-25. There we don't even have a file separation,
so if someone misses the head comment separating I/O from GS, a new
function can end up under the wrong API.
Maybe as Stefan suggests below we can at least split the function
pointers in two separate structs, with bdrv_state_* and bdrv_io_* struct
naming conventions.
But anyways thank you for the suggestions, I will add them to my TODO list.
Emanuele
>>
>> It would make life easier if we had distinct namning conventions
>> for APIs/struct/contsants in the respective headers.
>>
>> eg instead of "bdrv_" have "bdrv_state_" and "bdrv_io_" as
>> the two naming conventions for -global-state.h and -io.h
>> respectively, nad only use the bare 'bdrv_' for -common.h
>>
>> Yes, this would be major code churn, but I think it'd make
>> the code clearer to understand which will be a win over the
>> long term.
>>
>> NB, I'm not suggesting doing a rename as part of this patch
>> though. Any rename would have to be separate, and likely
>> split over many patches to make it manageable.
>
> Yes. Taking it one step further, BlockDriverState could be split into
> two struct so that I/O code doesn't even have access to the struct
> needed to invoke GS APIs. This is a type-safe way of enforcing the API
> split.
>
> Unfortunately that's a lot of code churn and I think the separation is
> not very clean. For example, block drivers need to forward requests to
> their children, so they need to traverse the graph (which we think of as
> global state).
>
> Stefan
>
next prev parent reply other threads:[~2021-10-08 7:28 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 14:31 [RFC PATCH v2 00/25] block layer: split block APIs in global state and I/O Emanuele Giuseppe Esposito
2021-10-05 14:31 ` [RFC PATCH v2 01/25] main-loop.h: introduce qemu_in_main_thread() Emanuele Giuseppe Esposito
2021-10-07 9:05 ` Stefan Hajnoczi
2021-10-05 14:31 ` [RFC PATCH v2 02/25] include/sysemu/block-backend: split header into I/O and global state (GS) API Emanuele Giuseppe Esposito
2021-10-07 9:13 ` Stefan Hajnoczi
2021-10-05 14:31 ` [RFC PATCH v2 03/25] block/block-backend.c: assertions for block-backend Emanuele Giuseppe Esposito
2021-10-05 16:29 ` Eric Blake
2021-10-06 9:36 ` Emanuele Giuseppe Esposito
2021-10-07 10:48 ` Stefan Hajnoczi
2021-10-05 14:31 ` [RFC PATCH v2 04/25] include/block/block: split header into I/O and global state API Emanuele Giuseppe Esposito
2021-10-07 9:33 ` Stefan Hajnoczi
2021-10-07 10:54 ` Emanuele Giuseppe Esposito
2021-10-07 11:51 ` Paolo Bonzini
2021-10-07 13:18 ` Eric Blake
2021-10-07 11:43 ` Daniel P. Berrangé
2021-10-07 13:01 ` Stefan Hajnoczi
2021-10-08 7:26 ` Emanuele Giuseppe Esposito [this message]
2021-10-05 14:31 ` [RFC PATCH v2 05/25] assertions for block " Emanuele Giuseppe Esposito
2021-10-07 10:44 ` Stefan Hajnoczi
2021-10-05 14:31 ` [RFC PATCH v2 06/25] include/block/block_int: split header into I/O and " Emanuele Giuseppe Esposito
2021-10-07 10:52 ` Stefan Hajnoczi
2021-10-07 11:30 ` Emanuele Giuseppe Esposito
2021-10-07 13:38 ` Stefan Hajnoczi
2021-10-05 14:31 ` [RFC PATCH v2 07/25] assertions for block_int " Emanuele Giuseppe Esposito
2021-10-07 14:19 ` Stefan Hajnoczi
2021-10-05 14:31 ` [RFC PATCH v2 08/25] block: introduce assert_bdrv_graph_writable Emanuele Giuseppe Esposito
2021-10-07 12:01 ` Paolo Bonzini
2021-10-07 12:02 ` Paolo Bonzini
2021-10-07 13:47 ` Emanuele Giuseppe Esposito
2021-10-07 14:18 ` Stefan Hajnoczi
2021-10-05 14:31 ` [RFC PATCH v2 09/25] include/block/blockjob_int.h: split header into I/O and GS API Emanuele Giuseppe Esposito
2021-10-07 14:21 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 10/25] assertions for blockjob_int.h Emanuele Giuseppe Esposito
2021-10-07 14:21 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 11/25] include/block/blockjob.h: global state API Emanuele Giuseppe Esposito
2021-10-07 14:23 ` Stefan Hajnoczi
2021-10-08 7:20 ` Emanuele Giuseppe Esposito
2021-10-11 11:10 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 12/25] assertions for blockob.h " Emanuele Giuseppe Esposito
2021-10-07 14:25 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 13/25] include/systemu/blockdev.h: " Emanuele Giuseppe Esposito
2021-10-07 12:00 ` Paolo Bonzini
2021-10-07 14:28 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 14/25] assertions for blockdev.h " Emanuele Giuseppe Esposito
2021-10-07 12:04 ` Paolo Bonzini
2021-10-07 14:29 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 15/25] include/block/snapshot: global state API + assertions Emanuele Giuseppe Esposito
2021-10-07 12:06 ` Paolo Bonzini
2021-10-07 14:31 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 16/25] block/backup-top.h: " Emanuele Giuseppe Esposito
2021-10-07 12:08 ` Paolo Bonzini
2021-10-07 14:32 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 17/25] include/block/transactions: " Emanuele Giuseppe Esposito
2021-10-07 14:47 ` Stefan Hajnoczi
2021-10-08 7:18 ` Emanuele Giuseppe Esposito
2021-10-05 14:32 ` [RFC PATCH v2 18/25] block/coroutines: I/O API Emanuele Giuseppe Esposito
2021-10-07 11:52 ` Paolo Bonzini
2021-10-07 14:47 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 19/25] block_int-common.h: split function pointers in BlockDriver Emanuele Giuseppe Esposito
2021-10-07 14:49 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 20/25] block_int-common.h: assertion in the callers of BlockDriver function pointers Emanuele Giuseppe Esposito
2021-10-07 14:50 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 21/25] block_int-common.h: split function pointers in BdrvChildClass Emanuele Giuseppe Esposito
2021-10-07 14:51 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 22/25] block_int-common.h: assertions in the callers of BdrvChildClass function pointers Emanuele Giuseppe Esposito
2021-10-07 14:51 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 23/25] block-backend-common.h: split function pointers in BlockDevOps Emanuele Giuseppe Esposito
2021-10-07 14:52 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 24/25] job.h: split function pointers in JobDriver Emanuele Giuseppe Esposito
2021-10-07 14:54 ` Stefan Hajnoczi
2021-10-08 10:48 ` Emanuele Giuseppe Esposito
2021-10-11 11:12 ` Stefan Hajnoczi
2021-10-05 14:32 ` [RFC PATCH v2 25/25] job.h: assertions in the callers of JobDriver funcion pointers Emanuele Giuseppe Esposito
2021-10-07 14:54 ` Stefan Hajnoczi
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=7b37f097-8f91-d8c2-f813-a0ce896da2d8@redhat.com \
--to=eesposit@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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;
as well as URLs for NNTP newsgroup(s).