[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20110812.025708.1569052368114569085.davem@davemloft.net>
Date: Fri, 12 Aug 2011 02:57:08 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: ja@....bg, netdev@...r.kernel.org
Subject: Re: [PATCH v2 net-next] neigh: reduce arp latency
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Tue, 09 Aug 2011 20:15:58 +0200
> Le mardi 09 août 2011 à 20:06 +0300, Julian Anastasov a écrit :
>
>> To be correct with old NUD_INCOMPLETE logic may be we can use
>> max(neigh->parms->retrans_time, HZ/2) here instead of HZ?
>>
>
> Thanks Julian a lot for reviewing, here is v2 adressing this point.
>
> [PATCH v2 net-next] neigh: reduce arp latency
>
> Remove the artificial HZ latency on arp resolution.
>
> Instead of firing a timer in one jiffy (up to 10 ms if HZ=100), lets
> send the ARP message immediately.
>
> Before patch :
>
> # arp -d 192.168.20.108 ; ping -c 3 192.168.20.108
> PING 192.168.20.108 (192.168.20.108) 56(84) bytes of data.
> 64 bytes from 192.168.20.108: icmp_seq=1 ttl=64 time=9.91 ms
> 64 bytes from 192.168.20.108: icmp_seq=2 ttl=64 time=0.065 ms
> 64 bytes from 192.168.20.108: icmp_seq=3 ttl=64 time=0.061 ms
>
> After patch :
>
> $ arp -d 192.168.20.108 ; ping -c 3 192.168.20.108
> PING 192.168.20.108 (192.168.20.108) 56(84) bytes of data.
> 64 bytes from 192.168.20.108: icmp_seq=1 ttl=64 time=0.152 ms
> 64 bytes from 192.168.20.108: icmp_seq=2 ttl=64 time=0.064 ms
> 64 bytes from 192.168.20.108: icmp_seq=3 ttl=64 time=0.074 ms
>
> Signed-off-by: Eric Dumazet <eric.dumazet@...il.com>
Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists