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 38378ECAAA1 for ; Mon, 24 Oct 2022 18:03:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230238AbiJXSD2 (ORCPT ); Mon, 24 Oct 2022 14:03:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40798 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230123AbiJXSCr (ORCPT ); Mon, 24 Oct 2022 14:02:47 -0400 Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 82B7F2BE24 for ; Mon, 24 Oct 2022 09:43:27 -0700 (PDT) Received: by mail-qk1-x72a.google.com with SMTP id d13so6409480qko.5 for ; Mon, 24 Oct 2022 09:43:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=PQUAOIAwlBb1Ac+IMwvAIs+PccHrMcnmJEUvE59sduo=; b=jewwKjOp110j3RCbj7CHLjBE8dKB97kT3YOWZrJPH+I0aKVAMllj00IyW4LjSUObNq xZxAev3oxd6QAV4hE5YaXUEwQ94oeJowwRgOVnBVYCVeLA7+SgH23Crl+teu7+moouXr gfuNjRMaQKPr6BvDDAGWe6LVGeKCG8OaK80wRHJUeGWx6m0v2AdBntfj/jIHl2MmQb9n mm8j4G9pPI7B2/mhfoyv1MaZ6w8ykxNfmPwYLQHr9h0ZLbQq4ZWPG3HllMuO/v4hz27Q 6gbNQv12/D6WvhnQQUceQqVe8ihCDkBq5rmJBdOlJce/N4Nz7zGsAJlwQp0R9/ienRWm brBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PQUAOIAwlBb1Ac+IMwvAIs+PccHrMcnmJEUvE59sduo=; b=0HoB6SPz2Ekyy0+dHYsbuG4FoWa5Rwoszve9jgNHPbqJ4XPBdPsaUSONmRBvFMECgc n71iWSpmm/LReEm4SCZ1Q3EWwxCvN6yRsG/pjhYbMOoyG2mzKqANVxAmqpK8HemZb6cs +60RgSYcXdN4wnfI8bBldX6zWtxMXioyHfZfhTp7iF09GUfu2AyMUDhT+60r4pnGbc5/ DSLmM0BpLF9HbHofZTH304Eg5Yowc7mexY+Vo4YUZtNEMP8Fq2SVRjaGhHsItjkmlgbU c5lH9dkDG5shkR2C7nBRUQ5iOlpYiyeGhjWqRbhxS9MkQ8WmNQf+QW4wk8uRy5ezUmHi pWNg== X-Gm-Message-State: ACrzQf1VKVIjKx4+fZqtPr0EsjOkXYQLWP3VUdjqAAy6Frqzeq9pETpj CDa8TFsuQszfsDtYSMGDYJ7QPg== X-Google-Smtp-Source: AMsMyM4MXMW3GmPJvEEh/mqAM/OPAdIuvpMk9/nnN9yyv8FxhAGbMQqjRxi5gOjjZPTaf43M0wJ8fQ== X-Received: by 2002:a05:620a:1a82:b0:6ee:d1b9:95b7 with SMTP id bl2-20020a05620a1a8200b006eed1b995b7mr23057529qkb.128.1666629691890; Mon, 24 Oct 2022 09:41:31 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-47-55-122-23.dhcp-dynamic.fibreop.ns.bellaliant.net. [47.55.122.23]) by smtp.gmail.com with ESMTPSA id s17-20020a05620a29d100b006bbf85cad0fsm275754qkp.20.2022.10.24.09.41.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Oct 2022 09:41:31 -0700 (PDT) Received: from jgg by wakko with local (Exim 4.95) (envelope-from ) id 1on0W2-00DXTk-FI; Mon, 24 Oct 2022 13:41:30 -0300 Date: Mon, 24 Oct 2022 13:41:30 -0300 From: Jason Gunthorpe To: Dust Li Cc: Yanjun Zhu , Zhu Yanjun , leon@kernel.org, linux-rdma@vger.kernel.org Subject: Re: [PATCH 0/3] RDMA net namespace Message-ID: References: <20221024011007.GE63658@linux.alibaba.com> <20221023220450.2287909-1-yanjun.zhu@intel.com> <20221024115228.GF63658@linux.alibaba.com> <662d6804-0e16-117e-d4a4-9abd4a2e8c75@linux.dev> <20221024143521.GG63658@linux.alibaba.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221024143521.GG63658@linux.alibaba.com> Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org On Mon, Oct 24, 2022 at 10:35:21PM +0800, Dust Li wrote: > For the netdevice, that's true. But for RDMA, we should not even see > the ib device in the containers any more, so I think we cannot create > qp/cq, and RDMA is not available for these containers in this case. Correct, in shared mode the RDMA device should only allow using GID table entries that have netdevs that are present in the processe's net namespace. This is, in general, the philosophy. The user is supposed to keep the various devices in the namespace in sync, because the kernel cannot guess what is correct. Jason