All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: linux-rdma@vger.kernel.org, zyjzyj2000@gmail.com, jgg@ziepe.ca,
	linux-kernel@vger.kernel.org, rpearsonhpe@gmail.com,
	Daisuke Matsuda <matsuda-daisuke@fujitsu.com>,
	Zhu Yanjun <yanjun.zhu@linux.dev>
Subject: Re: [PATCH for-next v3 2/2] RDMA/rxe: Call rxe_set_mtu after rxe_register_device
Date: Mon, 18 Sep 2023 15:37:10 +0300	[thread overview]
Message-ID: <20230918123710.GD103601@unreal> (raw)
In-Reply-To: <20230918020543.473472-2-lizhijian@fujitsu.com>

On Mon, Sep 18, 2023 at 10:05:43AM +0800, Li Zhijian wrote:
> rxe_set_mtu() will call rxe_info_dev() to print message, and
> rxe_info_dev() expects dev_name(rxe->ib_dev->dev) has been assigned.
> 
> Previously since dev_name() is not set, when a new rxe link is being
> added, 'null' will be used as the dev_name like:
> 
> "(null): rxe_set_mtu: Set mtu to 1024"
> 
> Move rxe_register_device() earlier to assign the correct dev_name
> so that it can be read by rxe_set_mtu() later.

I would expect removal of that print line instead of moving
rxe_register_device().

Thanks

> 
> And it's safe to do such change since mtu will not be used during the
> rxe_register_device()
> 
> After this change, the message becomes:
> "rxe_eth0: rxe_set_mtu: Set mtu to 4096"
> 
> Fixes: 9ac01f434a1e ("RDMA/rxe: Extend dbg log messages to err and info")
> Reviewed-by: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
> Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> ---
>  drivers/infiniband/sw/rxe/rxe.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/infiniband/sw/rxe/rxe.c b/drivers/infiniband/sw/rxe/rxe.c
> index a086d588e159..8a43c0c4f8d8 100644
> --- a/drivers/infiniband/sw/rxe/rxe.c
> +++ b/drivers/infiniband/sw/rxe/rxe.c
> @@ -169,10 +169,13 @@ void rxe_set_mtu(struct rxe_dev *rxe, unsigned int ndev_mtu)
>   */
>  int rxe_add(struct rxe_dev *rxe, unsigned int mtu, const char *ibdev_name)
>  {
> +	int ret;
> +
>  	rxe_init(rxe);
> +	ret = rxe_register_device(rxe, ibdev_name);
>  	rxe_set_mtu(rxe, mtu);
>  
> -	return rxe_register_device(rxe, ibdev_name);
> +	return ret;
>  }
>  
>  static int rxe_newlink(const char *ibdev_name, struct net_device *ndev)
> -- 
> 2.29.2
> 

  reply	other threads:[~2023-09-18 12:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  2:05 [PATCH for-next v3 1/2] RDMA/rxe: Improve newline in printing messages Li Zhijian
2023-09-18  2:05 ` [PATCH for-next v3 2/2] RDMA/rxe: Call rxe_set_mtu after rxe_register_device Li Zhijian
2023-09-18 12:37   ` Leon Romanovsky [this message]
2023-09-19  0:57     ` Zhijian Li (Fujitsu)
2023-09-19  1:11       ` Zhu Yanjun
2023-09-19  3:25         ` Zhijian Li (Fujitsu)
2023-09-19  4:01           ` Zhu Yanjun
2023-09-19  8:19           ` Leon Romanovsky
2023-09-20 10:24             ` Zhijian Li (Fujitsu)
2023-09-18  7:26 ` [PATCH for-next v3 1/2] RDMA/rxe: Improve newline in printing messages Zhu Yanjun

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=20230918123710.GD103601@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lizhijian@fujitsu.com \
    --cc=matsuda-daisuke@fujitsu.com \
    --cc=rpearsonhpe@gmail.com \
    --cc=yanjun.zhu@linux.dev \
    --cc=zyjzyj2000@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.