Subject: Re: [PATCH] lockd: NSMPROC_MON should be send only once even if in
 multithread
To:     Chuck Lever <chucklever@gmail.com>
CC:     Bruce Fields <bfields@fieldses.org>,
        Jeff Layton <jlayton@kernel.org>,
        Trond Myklebust <trond.myklebust@hammerspace.com>,
        Anna Schumaker <anna.schumaker@netapp.com>,
        Linux NFS Mailing List <linux-nfs@vger.kernel.org>
References: <1547705746-69554-1-git-send-email-zhangxiaoxu5@huawei.com>
 <4E812155-4DB4-4EF4-91ED-EDBB1B0BBFF7@gmail.com>
From:   "zhangxiaoxu (A)" <zhangxiaoxu5@huawei.com>
Message-ID: <00390d85-d2dd-be57-4192-bff562a75684@huawei.com>
Date:   Fri, 18 Jan 2019 10:48:35 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <4E812155-4DB4-4EF4-91ED-EDBB1B0BBFF7@gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk


On 1/17/2019 10:33 PM, Chuck Lever wrote:
> Hi, what is the harm of sending more than one MON request for a peer?
Maybe no harm.
The rpc.statd won't record the peer twice.

I found this when I tested the xfstest generic/089.
The rpc task for that msg sometimes take very long time.
rpc took 57 sec who t_mtab/2377 srv rpc.statd xid 2453489031 prog statd/100024/1 proc 2 prot 6 flags 0x680

I think the msg just send only one time is enough.
RPC and rpc.statd maybe consume for a long time on the network.