Re: [PATCH 2/2] nbd: change a parameter's type to remove a memcpycall

[Paul Clements]

Denis Cheng wrote:
> this memcpy looks so strange, in fact it's merely a pointer dereference,
> so I change the parameter's type to refer it more directly,
> this could make the memcpy not needed anymore.
>
> in the function nbd_read_stat where nbd_find_request is only once called,
> the parameter served should be transformed accordingly.

This is really a matter of preference. The generated code ends up being 
about the same, I think, while your patch makes the call to 
nbd_find_request kind of obtuse. Also, the memcpy's are balanced between 
send_req and find_request, so you can quickly see how the data is being 
transferred (from req into handle, and then back again). Your patch 
makes this less clear, at least to me.

--
Paul


> Signed-off-by: Denis Cheng <crquan@xxxxxxxxx>
> ---
>  drivers/block/nbd.c |    7 ++-----
>  1 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
> index 86639c0..a4d8508 100644
> --- a/drivers/block/nbd.c
> +++ b/drivers/block/nbd.c
> @@ -235,14 +235,11 @@ error_out:
>  	return 1;
>  }
>  
> -static struct request *nbd_find_request(struct nbd_device *lo, char *handle)
> +static struct request *nbd_find_request(struct nbd_device *lo, struct request *xreq)
>  {
>  	struct request *req, *n;
> -	struct request *xreq;
>  	int err;
>  
> -	memcpy(&xreq, handle, sizeof(xreq));
> -
>  	err = wait_event_interruptible(lo->active_wq, lo->active_req != xreq);
>  	if (unlikely(err))
>  		goto out;
> @@ -297,7 +294,7 @@ static struct request *nbd_read_stat(struct nbd_device *lo)
>  		goto harderror;
>  	}
>  
> -	req = nbd_find_request(lo, reply.handle);
> +	req = nbd_find_request(lo, *(struct request **)reply.handle);
>  	if (unlikely(IS_ERR(req))) {
>  		result = PTR_ERR(req);
>  		if (result != -ENOENT)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/