From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C9441C433FE for ; Tue, 11 Oct 2022 10:12:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229453AbiJKKM3 (ORCPT ); Tue, 11 Oct 2022 06:12:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43964 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229446AbiJKKM2 (ORCPT ); Tue, 11 Oct 2022 06:12:28 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D02D326FB for ; Tue, 11 Oct 2022 03:12:27 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 746626116F for ; Tue, 11 Oct 2022 10:12:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4B906C433D6; Tue, 11 Oct 2022 10:12:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1665483146; bh=ut+CPf24xnDu/Di2W9l+Dt15v5saTJMQ/nDnos7WWrE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HhvcqAkbm7DL1PGTHAKopcHQ/TJjxV1ZGdpvEJvsw5kq6eMidOUb4zSN9I1XYgeZP YEkmz3WbaRBT4wVJyADop85riAqORUQyv0iSeTzG+LzB+x8K8C2jvBj/kdlh2Rf016 kZCwGiR8ffZV5ILVX7gKDIl8/u/OurtzxkWQxoaw9700ok/LauA1GlodS+uErEKiom WrOjIggHpOet/h/mbJGA0oLFkdZjlwu7WKa05tBV1kyizbHaIdXRch5H5+loVlYpST bmkkT7JJOG98Counc1bz8l0mj6naweW+kNmjbf6zt7l/AIsxw5+lJ+s0svye6sIOee AE/7hHRJhOSyg== Date: Tue, 11 Oct 2022 13:12:22 +0300 From: Leon Romanovsky To: Zhu Yanjun Cc: yanjun.zhu@linux.dev, jgg@nvidia.com, leo@kernel.org, linux-rdma@vger.kernel.org Subject: Re: [RFC PATCH 1/1] RDMA/core: Fix a problem from rdma link in exclusive mode Message-ID: References: <20221011002545.1410247-1-yanjun.zhu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221011002545.1410247-1-yanjun.zhu@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Mon, Oct 10, 2022 at 08:25:45PM -0400, Zhu Yanjun wrote: > From: Zhu Yanjun > > This is not an official commit. In rdma net namespace, the rdma device > is separate from the net device. For example, a rdma device A is in net > namespace A1 while the related net device B is in net namespace B1. > > I am curious how to make perftest and rping tests on the above > scenario. The ip address of net device B is in net namespace B1 > while the rdma device is in net namespace A1. Use "exclusive" mode, "shared" is legacy interface for backward compatibility. > > From my perspective, the rdma device and related net device should > be in the same net namespace. When a net device is moved from one net > namespace to another net namespace, the rdma device should be in the > same net namespace with the net device. > > In this commit, when all the ib devices are parsed in exclusive mode, > if the ib devices and related net devices are not in the same net > namespace, the link information will not be reported to user space. > > This commit is a RFC. Please don't send patches as reply-to. Thanks