Re: [9fans] cpu command latency

[Kenny Lasse Hoff Levinsen <kennylevinsen@gmail.com>]

Your loop only seems to dials the server once, then reuses the channel from /srv. 9fs(4) is just a convenience wrapper for common hosts and tasks that ultimately calls srv(4) and mount(1) as necessary - if the channel exists, it is simply a call to mount(1), which translates to an attach(5) 9P message on the existing connection.

Delete the channel from /srv in the loop to test a full remote mount dance, including the initial dial. It shouldn't take 3s to dial, though.

Best regards,
Kenny Levinsen

> On 11. maj 2016, at 15.12, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
> 
> thanks charles for your quick response.
> 
> the times below are mount latency just after rebooting.
> the first is much larger than others.
> 0.00u 0.00s 3.73r     9fs sources
> 0.00u 0.00s 0.71r     9fs sources
> 0.00u 0.00s 0.21r     9fs sources
> with the script below:
> for(i in 1 2 3){
>        time 9fs $host
>        unmount /n/$host
>        sleep 3
>    }
> }
> 
> probably cpu command latency will show similar behavior with much more time.
> 
> Kenji Arisawa
> 
>