netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Xu Wang <vulab@iscas.ac.cn>
Cc: santosh.shilimkar@oracle.com, davem@davemloft.net,
	kuba@kernel.org, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rds: send: Replace sg++ with sg = sg_next(sg)
Date: Wed, 8 Jul 2020 08:34:18 +0300	[thread overview]
Message-ID: <20200708053418.GP207186@unreal> (raw)
In-Reply-To: <20200708034252.17408-1-vulab@iscas.ac.cn>

On Wed, Jul 08, 2020 at 03:42:52AM +0000, Xu Wang wrote:
> Replace sg++ with sg = sg_next(sg).
>
> Signed-off-by: Xu Wang <vulab@iscas.ac.cn>
> ---
>  net/rds/send.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/rds/send.c b/net/rds/send.c
> index 68e2bdb08fd0..57d03a6753de 100644
> --- a/net/rds/send.c
> +++ b/net/rds/send.c
> @@ -387,7 +387,7 @@ int rds_send_xmit(struct rds_conn_path *cp)
>  				ret -= tmp;
>  				if (cp->cp_xmit_data_off == sg->length) {
>  					cp->cp_xmit_data_off = 0;
> -					sg++;
> +					sg = sg_next(sg);

What about rest cases?

➜  kernel git:(rdma-next) git grep "sg++" net/rds/
net/rds/message.c:              sg++;
net/rds/message.c:                      sg++;
net/rds/message.c:                      sg++;
net/rds/send.c:                                 sg++;
net/rds/tcp_send.c:                     sg++;

Thanks

>  					cp->cp_xmit_sg++;
>  					BUG_ON(ret != 0 && cp->cp_xmit_sg ==
>  					       rm->data.op_nents);
> --
> 2.17.1
>

      reply	other threads:[~2020-07-08  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08  3:42 [PATCH] rds: send: Replace sg++ with sg = sg_next(sg) Xu Wang
2020-07-08  5:34 ` Leon Romanovsky [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=20200708053418.GP207186@unreal \
    --to=leon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=santosh.shilimkar@oracle.com \
    --cc=vulab@iscas.ac.cn \
    /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).