[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140729.155050.311148635959938226.davem@davemloft.net>
Date: Tue, 29 Jul 2014 15:50:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: himangi774@...il.com
Cc: trond.myklebust@...marydata.com, bfields@...ldses.org,
linux-nfs@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, julia.lawall@...6.fr
Subject: Re: [PATCH] svcrdma: delete double assignment
From: Himangi Saraogi <himangi774@...il.com>
Date: Mon, 28 Jul 2014 20:59:38 +0530
> Delete successive assignments to the same location.
>
> A simplified version of Coccinelle semantic match that finds this problem is as
> follows:
>
> // <smpl>
> @@
> expression i;
> @@
>
> *i = ...;
> i = ...;
> // </smpl>
>
> Signed-off-by: Himangi Saraogi <himangi774@...il.com>
I am not so sure about this change either.
> @@ -956,7 +956,6 @@ static struct svc_xprt *svc_rdma_accept(struct svc_xprt *xprt)
> dprintk("svcrdma: failed to create QP, ret=%d\n", ret);
> goto errout;
> }
> - newxprt->sc_max_sge = qp_attr.cap.max_send_sge;
> newxprt->sc_max_sge = qp_attr.cap.max_recv_sge;
> newxprt->sc_sq_depth = qp_attr.cap.max_send_wr;
> newxprt->sc_max_requests = qp_attr.cap.max_recv_wr;
->sc_max_sge is used to limit the number of segments used during sends,
currently in this code. Grep for where it is used.
Therefore, if anything, the correct thing to do would be to retain the
first line rather than the second line.
Someone who actually works on this code and understands it should
really take a close look at this before anyone even thinks about
applying this patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists