Received: by 2002:a05:7412:e794:b0:fa:551:50a7 with SMTP id o20csp1534249rdd; Thu, 11 Jan 2024 01:59:40 -0800 (PST) X-Google-Smtp-Source: AGHT+IHr2dnnqC2eG9bjcHGegdLmtRkt7RkHnMbnLKNkNedWOativrWFJwKAUajv82QNjVaNw7a7 X-Received: by 2002:a17:906:4958:b0:a28:abfa:e405 with SMTP id f24-20020a170906495800b00a28abfae405mr532714ejt.58.1704967180069; Thu, 11 Jan 2024 01:59:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704967180; cv=none; d=google.com; s=arc-20160816; b=pfN25Gqq/h7AozADYWfCR43D5703XfdFiuYx6QGOKYkidBslC1V4UdzwByzcTwHL0E kYsybjpyHv7iPMMNV8oV6rdAMLkwLHV+jkT62CvxobfiJIWni/3b9jw7TaWSZF+xnkyB VsXCAT/9OGNFHutX9TQ9nv1oA2HBl4CZIPdeLkP12SP2SR5ccIRxgHoPnbrP3K7RGJFO 7c7t69lEdecVYRBGGT+1O1JZgkylE5xONZy+OgvvfDLhs/25duOy28OaRaVc+9WEl/A3 F4UegxP0imNLNX304h9QYDZgrR8Ag30bO76qWbhJol0LhwyBRAxluwWaIvWkKG/usi/3 Kn+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:list-unsubscribe:list-subscribe:list-id:precedence :references:message-id:subject:cc:to:from:date:dkim-signature; bh=2Dk1K4oA3lTS7vW3hThzV0/Ha1dlpB2OLy1kuXUpx/o=; fh=6ohaWxFsxNbYiEnfdNErfeXdcA7pFXErTgr8wdvWvco=; b=aAn1rUZzEDVSTilsKAi65WfWz3NweykJUhbJNJt7EJtkjwBBp3210cHklRzSq/68Eu EwEdMli4LHxx1StFvPZN1qgpoZbRTLnRmmtGt2kybFmdlg0y3FswLu1u3kENYl8O4EwM U2fUWCkRkGDcUQh8hbRC0J9Oz/i+mBNoRfR0f8ZIG9EWKNWIfao7ax8PBjA6rthuC5SF xDpI1YY/IYNSnKKx8ZLvCW71f0xoNmVlljSei1nNmZ1zw5MNnUHsbJ7VbbaMw57TCaaU LWa9MZ9mTM0b87AlflQ9Sd96nLEsaK5S0Qe8jIwCdipWWvtB+SFBAIVIein4bhwNg7yv /e8A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jD9Ganho; spf=pass (google.com: domain of linux-kernel+bounces-23348-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-23348-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id hb22-20020a170906b89600b00a2a13930388si341636ejb.624.2024.01.11.01.59.40 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Jan 2024 01:59:40 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-23348-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jD9Ganho; spf=pass (google.com: domain of linux-kernel+bounces-23348-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-23348-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id CDAAB1F26B22 for ; Thu, 11 Jan 2024 09:59:39 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id F401F12B86; Thu, 11 Jan 2024 09:59:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="jD9Ganho" Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2D1B511C85; Thu, 11 Jan 2024 09:59:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 59F5EC43394; Thu, 11 Jan 2024 09:59:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704967169; bh=1KGPvZ+Jg0PX+zqhJQSKMoD+l3+PBPpn18BXoSciB6Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jD9Ganho3AgqZxZXa2ui0CQk0kCwFljYXGvdhWYhpyWhLLxjiKN5jO11LGEMhDQmv ltSiSEoDchrykh8SbvtM3DWFiV6VjW20ML6HVpce+wBNEZhVcbNvpYmF2or32ccDyf iO5TcEgTtHQtYOY6PSXD2HzAv9TOWPlXv449dMqRYoiBcMeq5C82Z7/LM/aN9SEdGI F47obgCueOdlUkPCLZzLyR2a1sK0wQauokZmfBInPe00ttIm2rlqKisgY/VLQRiGko 1Q+0jyHycLWF+uLYCg7e+/9i9AsrrMVA0RArTDgP3h+TxCKBul4BkMhlhvqBqff/vP kDkUGGZalwzAg== Date: Thu, 11 Jan 2024 11:59:25 +0200 From: Leon Romanovsky To: "Zhijian Li (Fujitsu)" Cc: Greg Sword , "linux-rdma@vger.kernel.org" , "zyjzyj2000@gmail.com" , "jgg@ziepe.ca" , "linux-kernel@vger.kernel.org" , "rpearsonhpe@gmail.com" Subject: Re: [PATCH for-next v4 2/2] RDMA/rxe: Remove rxe_info from rxe_set_mtu Message-ID: <20240111095925.GB7488@unreal> References: <20240109083253.3629967-1-lizhijian@fujitsu.com> <20240109083253.3629967-2-lizhijian@fujitsu.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Wed, Jan 10, 2024 at 01:22:12AM +0000, Zhijian Li (Fujitsu) wrote: > > > On 09/01/2024 17:20, Greg Sword wrote: > > On Tue, Jan 9, 2024 at 4:41 PM Li Zhijian wrote: > >> > >> commit 9ac01f434a1e ("RDMA/rxe: Extend dbg log messages to err and info") > >> newly added this info. But it did only show null device when > >> the rdma_rxe is being loaded because dev_name(rxe->ib_dev->dev) > >> has not yet been assigned at the moment: > >> > >> "(null): rxe_set_mtu: Set mtu to 1024" > >> > >> Remove it to silent this message, check the mtu from it backend link > >> instead if needed. > >> > >> CC: Bob Pearson > >> Signed-off-by: Li Zhijian > >> --- > >> V4: Remove it rather than re-order rxe_set_mtu() and rxe_register_device() > >> --- > >> drivers/infiniband/sw/rxe/rxe.c | 2 -- > >> 1 file changed, 2 deletions(-) > >> > >> diff --git a/drivers/infiniband/sw/rxe/rxe.c b/drivers/infiniband/sw/rxe/rxe.c > >> index a086d588e159..ae466e72fc43 100644 > >> --- a/drivers/infiniband/sw/rxe/rxe.c > >> +++ b/drivers/infiniband/sw/rxe/rxe.c > >> @@ -160,8 +160,6 @@ void rxe_set_mtu(struct rxe_dev *rxe, unsigned int ndev_mtu) > >> > >> port->attr.active_mtu = mtu; > >> port->mtu_cap = ib_mtu_enum_to_int(mtu); > >> - > >> - rxe_info_dev(rxe, "Set mtu to %d\n", port->mtu_cap); > > > > I'd like to keep this statement so I can tell if the mtu setup was > > successful or not. > > During the module loading, once it's loaded successfully, the mtu is set as well. > > The another caller rxe_notify()->rxe_set_mtu() already had its own dbg message for this, > people can enable the dbg if needed. > > Anyway, I'm open to your point. IMHO, this print can be safely removed. Thanks > > > Thanks > Zhijian > > > > > >> } > >> > >> /* called by ifc layer to create new rxe device. > >> -- > >> 2.29.2 > >> > >>