From: Stefano Garzarella <sgarzare@redhat.com>
To: Anton Nefedov <anton.nefedov@virtuozzo.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Denis Lunev <den@virtuozzo.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v7 0/9] discard blockstats
Date: Thu, 6 Jun 2019 17:35:40 +0200 [thread overview]
Message-ID: <20190606153540.2v5g3kgd7g7ut5kr@steredhat> (raw)
In-Reply-To: <08293f58-121e-b26d-70b4-0c564fdbe095@virtuozzo.com>
On Tue, Jun 04, 2019 at 04:53:23PM +0000, Anton Nefedov wrote:
> On 3/6/2019 1:09 PM, Stefano Garzarella wrote:
> > On Tue, May 14, 2019 at 12:10:40PM +0000, Anton Nefedov wrote:
> >> hi,
> >>
> >> yet another take for this patch series; please kindly consider these for 4.1
> >>
> >> Just a few cosmetic comments were received for v6 so this is mostly
> >> a rebase+ping.
> >>
> >> new in v7:
> >> - general rebase
> >> - since clauses -> 4.1
> >> - patch 8: not completely trivial rebase: raw_account_discard moved to
> >> common raw_do_pdiscard()
> >> - patch 9: comment wording fixed
> >>
> >> v6: http://lists.nongnu.org/archive/html/qemu-devel/2018-11/msg06633.html
> >> v5: http://lists.nongnu.org/archive/html/qemu-devel/2018-10/msg06828.html
> >> v4: http://lists.nongnu.org/archive/html/qemu-devel/2018-08/msg04308.html
> >> v3: http://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg03688.html
> >>
> >
> > Hi Anton,
> > since qemu 4.0 added the discard support on virtio-blk, should we consider it
> > in this series?
> >
> > If you prefer I can work on it and send you the patch.
> >
>
> hi Stefano,
>
> if this series is finally getting in, it is really nice if you can add
> virtio-blk support too.
>
Sure, I'll do it!
Thanks,
Stefano
prev parent reply other threads:[~2019-06-06 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 12:10 [Qemu-devel] [PATCH v7 0/9] discard blockstats Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 1/9] qapi: group BlockDeviceStats fields Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 2/9] qapi: add unmap to BlockDeviceStats Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 3/9] block: add empty account cookie type Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 4/9] ide: account UNMAP (TRIM) operations Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 5/9] scsi: store unmap offset and nb_sectors in request struct Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 6/9] scsi: move unmap error checking to the complete callback Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 7/9] scsi: account unmap operations Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 8/9] file-posix: account discard operations Anton Nefedov
2019-05-14 12:10 ` [Qemu-devel] [PATCH v7 9/9] qapi: query-blockstat: add driver specific file-posix stats Anton Nefedov
2019-06-03 10:09 ` [Qemu-devel] [Qemu-block] [PATCH v7 0/9] discard blockstats Stefano Garzarella
2019-06-04 16:53 ` Anton Nefedov
2019-06-06 15:35 ` Stefano Garzarella [this message]
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=20190606153540.2v5g3kgd7g7ut5kr@steredhat \
--to=sgarzare@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@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 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).