Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp667767pxj; Fri, 14 May 2021 12:35:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxYGCdBsRKLWGkS7n8V5j4Pz/BRryVKxEiClSU0vtWjSccf5ptEPvMqmONOh+wfsbN4YFiA X-Received: by 2002:a17:907:1c15:: with SMTP id nc21mr51422393ejc.49.1621020924900; Fri, 14 May 2021 12:35:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621020924; cv=none; d=google.com; s=arc-20160816; b=j8Wxzp1oyFJ4sF5ggp7VhFthEpPvM3xhz7e7SyzjxMIY5b4HsEC3byJfto+MPVpB/T EnkU6GMZ4GXk5xXrsq3yT813LAbp44agt/kYz7hXwIRijEzd+WPYQqTKH5yOxncxqvqP nu/X/IWgsZ6PRIpGwQcuHxjWRop4GSHC9nyUvXi1KfwxYx8LuBwLd2/74eQyD9FXP52F pBmPX/cJgcu+01QwpW3z11KA0EiW8blERkEct4Wdu5LTMwwM8fm/gFFlsP0eUBqW8MmZ HsKqSiCFjiYJQOjvDrrqLVkYm1earkNdfNhH9rLTkn4XYGVNG6n3L8mwMgFJYNsPwom6 vprw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=36gOo3eX0E8dN0idvkT3iKZaKYtLseymasMxycOJSdA=; b=l4bJvT92fDNvcTBHavFMBYHeHDmFPytddLF+EGdLLS8B+iwaBZ7X/u/QeAGtcpLwuy eUq9uzr0YLa/wTx2LTdbcOaxkpp3EG0C+L/tenFOPkTfeZugq2GIG1cozRKd2O768WZT aktfvLqjeVLQWa2GAcv6GINGjzf0tI3Q8Ts7VXS8um1VUNImeVBZxcDmMdUAdbuwMOye +QfBpE0LItFF0vuAjy54aWR7GQsde6AQSxVkIriThsFgFiNemgUnY9NNLYBq4YzUqPXH tRGz/CB2wjU8Y/tEQxPhwy44OnHG4tHzfeMRSFw9zfGB0fyNT7suqTkLyFswyfUJ5aX/ iUFg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=R2nrIN0Z; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id jg13si9153785ejc.288.2021.05.14.12.35.01; Fri, 14 May 2021 12:35:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=R2nrIN0Z; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231840AbhENP7n (ORCPT + 99 others); Fri, 14 May 2021 11:59:43 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:40072 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231485AbhENP7m (ORCPT ); Fri, 14 May 2021 11:59:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1621007908; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=36gOo3eX0E8dN0idvkT3iKZaKYtLseymasMxycOJSdA=; b=R2nrIN0ZQJp4lYyUAKLWOAYJrrR/pgsDfOOshO3iRvJmFw77emNK9HJwpZVJ7o/sYQ1/ZU TF9OxNnq1goF4xiExeJsS8rmrbD0ZQMV8wYRp7iQCw82Af7zQpbqP1nB3O3JuWF8wVdaTW czfuRAsRNd0zgjF1c/8Nl4+HlWEmgpQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-563-BIN5oyoqMh6Qj6fpYEXe_g-1; Fri, 14 May 2021 11:58:26 -0400 X-MC-Unique: BIN5oyoqMh6Qj6fpYEXe_g-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2BFBD106BB29; Fri, 14 May 2021 15:58:25 +0000 (UTC) Received: from [172.16.176.1] (ovpn-64-2.rdu2.redhat.com [10.10.64.2]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5D5AA61156; Fri, 14 May 2021 15:58:24 +0000 (UTC) From: "Benjamin Coddington" To: "Olga Kornievskaia" Cc: "Dan Aloni" , "Trond Myklebust" , "Anna Schumaker" , linux-nfs Subject: Re: [PATCH v3 09/13] sunrpc: add a symlink from rpc-client directory to the xprt_switch Date: Fri, 14 May 2021 11:58:22 -0400 Message-ID: <3E3B831C-BCC3-462D-84D7-6D09E8EEDFDF@redhat.com> In-Reply-To: References: <20210426171947.99233-1-olga.kornievskaia@gmail.com> <20210426171947.99233-10-olga.kornievskaia@gmail.com> <20210427044214.vlbmbfdh5dpq4vhl@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On 14 May 2021, at 10:16, Olga Kornievskaia wrote: > On Fri, May 14, 2021 at 6:17 AM Benjamin Coddington > wrote: >> The information isn't lost, as the symlink points to the specific >> switch. >> Not using a number in the symlink name informs that there will only >> be one >> switch for each client and makes it more deterministic for users and >> software to navigate. > > What will be lost is that when you look at the xprt_switches directory > and see switch-1... switch-10 subdirectory, there is no way to tell > which rpc client uses which switch. Because each client-1 directory > will only have an entry saying "switch". > > Anyway, I submitted the new version but I think it's not as good as > the original. Hmm, ok - will we ever need to traverse objects in that direction though? I'm thinking that operations on xprts/rpcs will always start from a mount perspective from the admin, but really the root object is struct nfs_server, or bdi. I'm thinking of something like: /sys/fs/nfs//rpc_clnt -> ../../net/sunrpc/clnt-0 /sys/fs/nfs//volumes ... I suppose though you could have something monitoring the xprts, and upon finding a particular state would want to navigate back up to see what client is affected. At that point you'd have to read all the symlinks for all the rpc_clients. Ben