From: Jeff Cody <jcody@redhat.com>
To: Josh Durgin <jdurgin@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/4] rbd: remove unused constants and fields
Date: Tue, 30 Jun 2015 15:47:15 -0400 [thread overview]
Message-ID: <20150630194715.GD13877@localhost.localdomain> (raw)
In-Reply-To: <1433993326-26294-2-git-send-email-jdurgin@redhat.com>
On Wed, Jun 10, 2015 at 08:28:43PM -0700, Josh Durgin wrote:
> RBDAIOCB.status was only used for cancel, which was removed in
> 7691e24dbebb46658e89b3f950fda6ec78bbb823.
>
> RBDAIOCB.sector_num was never used.
>
> RADOSCB.done and rcbid were never used.
>
> RBD_FD* are obsolete since the pipe was removed in
> e04fb07fd1676e9facd7f3f878c1bbe03bccd26b.
>
> Signed-off-by: Josh Durgin <jdurgin@redhat.com>
> ---
> block/rbd.c | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/block/rbd.c b/block/rbd.c
> index fbe87e0..50b5f6b 100644
> --- a/block/rbd.c
> +++ b/block/rbd.c
> @@ -74,25 +74,18 @@ typedef struct RBDAIOCB {
> QEMUIOVector *qiov;
> char *bounce;
> RBDAIOCmd cmd;
> - int64_t sector_num;
> int error;
> struct BDRVRBDState *s;
> - int status;
> } RBDAIOCB;
>
> typedef struct RADOSCB {
> - int rcbid;
> RBDAIOCB *acb;
> struct BDRVRBDState *s;
> - int done;
> int64_t size;
> char *buf;
> int64_t ret;
> } RADOSCB;
>
> -#define RBD_FD_READ 0
> -#define RBD_FD_WRITE 1
> -
> typedef struct BDRVRBDState {
> rados_t cluster;
> rados_ioctx_t io_ctx;
> @@ -405,7 +398,6 @@ static void qemu_rbd_complete_aio(RADOSCB *rcb)
> }
> qemu_vfree(acb->bounce);
> acb->common.cb(acb->common.opaque, (acb->ret > 0 ? 0 : acb->ret));
> - acb->status = 0;
>
> qemu_aio_unref(acb);
> }
> @@ -621,7 +613,6 @@ static BlockAIOCB *rbd_start_aio(BlockDriverState *bs,
> acb->error = 0;
> acb->s = s;
> acb->bh = NULL;
> - acb->status = -EINPROGRESS;
>
> if (cmd == RBD_AIO_WRITE) {
> qemu_iovec_to_buf(acb->qiov, 0, acb->bounce, qiov->size);
> @@ -633,7 +624,6 @@ static BlockAIOCB *rbd_start_aio(BlockDriverState *bs,
> size = nb_sectors * BDRV_SECTOR_SIZE;
>
> rcb = g_new(RADOSCB, 1);
> - rcb->done = 0;
> rcb->acb = acb;
> rcb->buf = buf;
> rcb->s = acb->s;
> --
> 1.9.1
>
Reviewed-by: Jeff Cody <jcody@redhat.com>
next prev parent reply other threads:[~2015-06-30 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 3:28 [Qemu-devel] [PATCH 0/4] rbd cleanup and settings precedence fixes Josh Durgin
2015-06-11 3:28 ` [Qemu-devel] [PATCH 1/4] rbd: remove unused constants and fields Josh Durgin
2015-06-30 19:47 ` Jeff Cody [this message]
2015-06-11 3:28 ` [Qemu-devel] [PATCH 2/4] MAINTAINERS: update email address Josh Durgin
2015-06-30 19:47 ` Jeff Cody
2015-06-11 3:28 ` [Qemu-devel] [PATCH 3/4] rbd: make qemu's cache setting override any ceph setting Josh Durgin
2015-06-30 19:47 ` Jeff Cody
2015-06-11 3:28 ` [Qemu-devel] [PATCH 4/4] rbd: fix ceph settings precedence Josh Durgin
2015-06-30 18:28 ` [Qemu-devel] [PATCH 0/4] rbd cleanup and settings precedence fixes Josh Durgin
2015-07-09 9:59 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-07-14 14:20 ` Kevin Wolf
2015-07-14 19:42 ` Josh Durgin
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=20150630194715.GD13877@localhost.localdomain \
--to=jcody@redhat.com \
--cc=jdurgin@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).