Re: [PATCH] lockd: NSMPROC_MON should be send only once even if in multithread

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 1/19/2019 4:59 AM, Chuck Lever wrote:


On Jan 17, 2019, at 9:48 PM, zhangxiaoxu (A) <zhangxiaoxu5@xxxxxxxxxx> wrote:



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

MON is supposed to be a call to a local service (on the same host).
It would be interesting if you could determine why it takes so long.

Yes, I'm working for that.
I think this is an optimization point.
Why do we have to send multiple requests?

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


--
Chuck Lever
chucklever@xxxxxxxxx









[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux