All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	Eric Blake <eblake@redhat.com>,
	qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 03/12] dirty-bitmap: Drop unused functions
Date: Thu, 13 Apr 2017 12:57:00 -0400	[thread overview]
Message-ID: <3d2bce13-66cd-4d2c-3382-9964fc70400a@redhat.com> (raw)
In-Reply-To: <077cd9f0-110a-f2ea-fcf9-31b6f4c8b2c1@virtuozzo.com>



On 04/13/2017 05:19 AM, Vladimir Sementsov-Ogievskiy wrote:
> 13.04.2017 02:40, John Snow wrote:
>>
>> On 04/12/2017 07:36 PM, Eric Blake wrote:
>>> On 04/12/2017 05:47 PM, John Snow wrote:
>>>>
>>>> On 04/12/2017 01:49 PM, Eric Blake wrote:
>>>>> We had several functions that no one was using, and which used
>>>>> sector-based interfaces.  I'm trying to convert towards byte-based
>>>>> interfaces, so it's easier to just drop the unused functions:
>>>>>
>>>>> bdrv_dirty_bitmap_size
>>>>> bdrv_dirty_bitmap_get_meta
>>>>> bdrv_dirty_bitmap_reset_meta
>>>>> bdrv_dirty_bitmap_meta_granularity
>>>>>
>>>>> Signed-off-by: Eric Blake <eblake@redhat.com>
>>>>> ---
>>>>>   include/block/dirty-bitmap.h |  8 --------
>>>>>   block/dirty-bitmap.c         | 34 ----------------------------------
>>>>>   2 files changed, 42 deletions(-)
>>>>>
>>>> I think it's likely Vladimir is or at least was relying on some of
>>>> these
>>>> for his migration and persistence series.
>>>>
>>>> Might be nice to let him chime in to see how much of a hassle this is.
>>> Then let's add him in cc ;)
>>>
>> Err... I can't just summon people by mentioning them?
>>
>>> I'm okay if these functions stay because they have a user, but it would
>>> also be nice if they were properly byte-based (like everything else in
>>> dirty-bitmap at the end of my series).  So even if we remove them here,
>>> we can revert the removal, and re-add them but with a sane interface.
>>>
>> OK, but I will offer to do the work in the interest of not slowing
>> things down any further.
>>
>> Do you use any of these, Vladimir?
>>
>> --js
> HI all!
> 
> only bdrv_dirty_bitmap_size() is used. No problem to add it back with my
> series next update
> 
> 

Excellent, thanks!

In that case:

Reviewed-by: John Snow <jsnow@redhat.com>

Should be for the whole series, IIRC.

--js

  reply	other threads:[~2017-04-13 16:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 17:49 [Qemu-devel] [PATCH 00/12] make dirty-bitmap byte-based Eric Blake
2017-04-12 17:49 ` [Qemu-devel] [PATCH 01/12] dirty-bitmap: Report BlockDirtyInfo.count in bytes, as documented Eric Blake
2017-04-12 22:43   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 02/12] migration: Don't lose errno across aio context changes Eric Blake
2017-04-12 22:44   ` John Snow
2017-04-18 20:02   ` Juan Quintela
2017-04-12 17:49 ` [Qemu-devel] [PATCH 03/12] dirty-bitmap: Drop unused functions Eric Blake
2017-04-12 22:47   ` John Snow
2017-04-12 23:36     ` Eric Blake
2017-04-12 23:40       ` John Snow
2017-04-13  9:19         ` Vladimir Sementsov-Ogievskiy
2017-04-13 16:57           ` John Snow [this message]
2017-04-12 17:49 ` [Qemu-devel] [PATCH 04/12] dirty-bitmap: Track size in bytes Eric Blake
2017-04-12 23:32   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 05/12] dirty-bitmap: Set iterator start by offset, not sector Eric Blake
2017-04-13  0:00   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 06/12] dirty-bitmap: Change bdrv_dirty_iter_next() to report byte offset Eric Blake
2017-04-13  0:10   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 07/12] dirty-bitmap: Change bdrv_get_dirty_count() to report bytes Eric Blake
2017-04-13  0:19   ` John Snow
2017-04-13  0:22   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 08/12] dirty-bitmap: Change bdrv_get_dirty() to take bytes Eric Blake
2017-04-13  0:25   ` John Snow
2017-04-13  0:48     ` Eric Blake
2017-04-12 17:49 ` [Qemu-devel] [PATCH 09/12] dirty-bitmap: Change bdrv_[re]set_dirty_bitmap() to use bytes Eric Blake
2017-04-13  0:29   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 10/12] mirror: Switch mirror_dirty_init() to byte-based iteration Eric Blake
2017-04-13  1:24   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 11/12] dirty-bitmap: Switch bdrv_set_dirty() to bytes Eric Blake
2017-04-13  1:28   ` John Snow
2017-04-12 17:49 ` [Qemu-devel] [PATCH 12/12] dirty-bitmap: Convert internal hbitmap size/granularity Eric Blake
2017-04-13  1:38   ` John Snow

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=3d2bce13-66cd-4d2c-3382-9964fc70400a@redhat.com \
    --to=jsnow@redhat.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --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 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.