diff options
| author | Eric Blake <eblake@redhat.com> | 2019-05-10 10:17:35 -0500 |
|---|---|---|
| committer | Eric Blake <eblake@redhat.com> | 2019-06-13 08:56:10 -0500 |
| commit | 416e34bd04bea32a6e68c103dbbb4210a1f1d0dd (patch) | |
| tree | db8c651d152cf3f4e28fc2ae923c32877d5b5be0 /gitdm.config | |
| parent | b28f582c2acaca26b66262d75cc5a0bd2764482c (diff) | |
| download | qemu-416e34bd04bea32a6e68c103dbbb4210a1f1d0dd.zip qemu-416e34bd04bea32a6e68c103dbbb4210a1f1d0dd.tar.gz qemu-416e34bd04bea32a6e68c103dbbb4210a1f1d0dd.tar.bz2 | |
nbd/server: Nicer spelling of max BLOCK_STATUS reply length
Commit 3d068aff (3.0) introduced NBD_MAX_BITMAP_EXTENTS as a limit on
how large we would allow a reply to NBD_CMD_BLOCK_STATUS to grow when
it is visiting a qemu:dirty-bitmap: context. Later, commit fb7afc79
(3.1) reused the constant to limit base:allocation context replies,
although the name is now less appropriate in that situation.
Rename things, and improve the macro to use units.h for better
legibility. Then reformat the comment to comply with checkpatch rules
added in the meantime. No semantic change.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20190510151735.29687-1-eblake@redhat.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Diffstat (limited to 'gitdm.config')
0 files changed, 0 insertions, 0 deletions