linux-um archives
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: anton.ivanov@cambridgegreys.com, linux-um@lists.infradead.org
Cc: richard@nod.at, hch@lst.de
Subject: Re: [PATCH 2/4] um: Clean-up command processing in UML UBD driver
Date: Tue, 13 Nov 2018 06:34:31 -0700	[thread overview]
Message-ID: <8a1d3dcb-ea52-e745-b961-ea51224d2405@kernel.dk> (raw)
In-Reply-To: <20181113115947.19290-3-anton.ivanov@cambridgegreys.com>

On 11/13/18 4:59 AM, anton.ivanov@cambridgegreys.com wrote:
> From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
> 
> Clean-up command processing and return BLK_STS_NOTSUP for
> uknown commands.
> 
> Signed-off-by: Anton Ivanov <anton.ivanov@cambridgegreys.com>
> ---
>  arch/um/drivers/ubd_kern.c | 64 ++++++++++++++++++++++++++++------------------
>  1 file changed, 39 insertions(+), 25 deletions(-)
> 
> diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
> index 331837f1f632..0f02373ef632 100644
> --- a/arch/um/drivers/ubd_kern.c
> +++ b/arch/um/drivers/ubd_kern.c
> @@ -1307,21 +1307,25 @@ static int ubd_queue_one_vec(struct blk_mq_hw_ctx *hctx, struct request *req,
>  		io_req->fds[0] = dev->fd;
>  	io_req->error = 0;
>  
> -	if (req_op(req) != REQ_OP_FLUSH) {
> -		io_req->fds[1] = dev->fd;
> -		io_req->cow_offset = -1;
> -		io_req->offset = off;
> +	if (bvec != NULL) {
>  		io_req->length = bvec->bv_len;
> -		io_req->sector_mask = 0;
> -		io_req->offsets[0] = 0;
> -		io_req->offsets[1] = dev->cow.data_offset;
>  		io_req->buffer = page_address(bvec->bv_page) + bvec->bv_offset;
> -		io_req->sectorsize = 1 << 9;
> +	} else {
> +		io_req->buffer = NULL;
> +		io_req->length = blk_rq_bytes(req);
> +	}
>  
> -		if (dev->cow.file) {
> -			cowify_req(io_req, dev->cow.bitmap,
> -				   dev->cow.bitmap_offset, dev->cow.bitmap_len);
> -		}
> +	io_req->sectorsize = UBD_SECTOR_SIZE;
> +	io_req->fds[1] = dev->fd;
> +	io_req->cow_offset = -1;
> +	io_req->offset = off;
> +	io_req->sector_mask = 0;
> +	io_req->offsets[0] = 0;
> +	io_req->offsets[1] = dev->cow.data_offset;
> +
> +	if (dev->cow.file) {
> +		cowify_req(io_req, dev->cow.bitmap,
> +			   dev->cow.bitmap_offset, dev->cow.bitmap_len);
>  	}
>  
>  	ret = os_write_file(thread_fd, &io_req, sizeof(io_req));
> @@ -1330,7 +1334,6 @@ static int ubd_queue_one_vec(struct blk_mq_hw_ctx *hctx, struct request *req,
>  			pr_err("write to io thread failed: %d\n", -ret);
>  		kfree(io_req);
>  	}
> -
>  	return ret;
>  }
>  
> @@ -1344,20 +1347,31 @@ static blk_status_t ubd_queue_rq(struct blk_mq_hw_ctx *hctx,
>  	blk_mq_start_request(req);
>  
>  	spin_lock_irq(&ubd_dev->lock);
> -
> -	if (req_op(req) == REQ_OP_FLUSH) {
> +	switch (req_op(req)) {
> +	/* operations with no lentgth/offset arguments */
> +	case REQ_OP_FLUSH:
>  		ret = ubd_queue_one_vec(hctx, req, 0, NULL);
> -	} else {
> -		struct req_iterator iter;
> -		struct bio_vec bvec;
> -		u64 off = (u64)blk_rq_pos(req) << 9;
> -
> -		rq_for_each_segment(bvec, req, iter) {
> -			ret = ubd_queue_one_vec(hctx, req, off, &bvec);
> -			if (ret < 0)
> -				goto out;
> -			off += bvec.bv_len;
> +		break;
> +	/* operations with bio_vec arguments */
> +	case REQ_OP_READ:
> +	case REQ_OP_WRITE:
> +		{
> +			struct req_iterator iter;
> +			struct bio_vec bvec;
> +			u64 off = (u64)blk_rq_pos(req) << 9;
> +
> +			rq_for_each_segment(bvec, req, iter) {
> +				ret = ubd_queue_one_vec(hctx, req, off, &bvec);
> +				if (ret < 0)
> +					goto out;
> +				off += bvec.bv_len;
> +			}
>  		}
> +		break;

This indentation is wrong/awkward. The usual style is:

	case REQ_OP_READ:
	case REQ_OP_WRITE: {
		struct req_iterator iter;
		struct bio_vec bvec;
		u64 off = (u64)blk_rq_pos(req) << 9;

		rq_for_each_segment(bvec, req, iter) {
			ret = ubd_queue_one_vec(hctx, req, off, &bvec);
			if (ret < 0)
				goto out;
			off += bvec.bv_len;
		}
		break;
		}

Apart from that, looks good to me.

-- 
Jens Axboe


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2018-11-13 13:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 11:59 Revised and fixed patchset anton.ivanov
2018-11-13 11:59 ` [PATCH 1/4] um: Switch to block-mq constants in the UML UBD driver anton.ivanov
2018-11-13 13:33   ` Jens Axboe
2018-11-14 15:32   ` Christoph Hellwig
2018-11-14 17:00     ` Jens Axboe
2018-11-14 17:04       ` Anton Ivanov
2018-11-13 11:59 ` [PATCH 2/4] um: Clean-up command processing in " anton.ivanov
2018-11-13 13:34   ` Jens Axboe [this message]
2018-11-14 15:28     ` Christoph Hellwig
2018-11-14 15:31       ` Anton Ivanov
2018-11-14 15:33         ` Christoph Hellwig
2018-11-13 11:59 ` [PATCH 3/4] um: Remove unsafe printks from the io thread anton.ivanov
2018-11-13 13:31   ` Jens Axboe
2018-11-13 11:59 ` [PATCH 4/4] um: Add support for DISCARD in the UBD Driver anton.ivanov
2018-11-13 13:40   ` Jens Axboe
2018-11-13 14:04     ` Anton Ivanov
2018-11-13 15:18       ` Jens Axboe
2018-11-13 15:32         ` Anton Ivanov
2018-11-13 15:49           ` Jens Axboe
2018-11-13 15:52             ` Anton Ivanov
2018-11-14 15:30   ` Christoph Hellwig
2018-11-14 15:35     ` Anton Ivanov
  -- strict thread matches above, loose matches on Subject: below --
2018-11-14  8:10 [PATCH 1/4] um: Switch to block-mq constants in the UML UBD driver anton.ivanov
2018-11-14  8:10 ` [PATCH 2/4] um: Clean-up command processing in " anton.ivanov
2018-11-14 17:09 [PATCH 1/4] um: Switch to block-mq constants in the " anton.ivanov
2018-11-14 17:09 ` [PATCH 2/4] um: Clean-up command processing in " anton.ivanov

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=8a1d3dcb-ea52-e745-b961-ea51224d2405@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=hch@lst.de \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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