there is problem in l2fwd_send_packet(). l2fwd and some other examples assume burst traffic. l2fwd doesn't send packet if qconf->tx_mbufs[port].len < MAX_PKT_BURST.
2014-03-27 9:56 GMT+09:00 Fred Pedrisa <fredhps10 at hotmail.com>: > It is just a ping test, from one PC to another, using 2 ports as a L2 > Bridge. > > 64 bytes from 192.168.2.249: icmp_seq=967 ttl=128 time=1630 ms > 64 bytes from 192.168.2.249: icmp_seq=968 ttl=128 time=5005 ms > 64 bytes from 192.168.2.249: icmp_seq=969 ttl=128 time=4004 ms > 64 bytes from 192.168.2.249: icmp_seq=970 ttl=128 time=3003 ms > 64 bytes from 192.168.2.249: icmp_seq=971 ttl=128 time=3661 ms > 64 bytes from 192.168.2.249: icmp_seq=972 ttl=128 time=2660 ms > 64 bytes from 192.168.2.249: icmp_seq=973 ttl=128 time=1660 ms > 64 bytes from 192.168.2.249: icmp_seq=974 ttl=128 time=3001 ms > 64 bytes from 192.168.2.249: icmp_seq=975 ttl=128 time=2001 ms > 64 bytes from 192.168.2.249: icmp_seq=976 ttl=128 time=1000 ms > 64 bytes from 192.168.2.249: icmp_seq=977 ttl=128 time=0.713 ms > 64 bytes from 192.168.2.249: icmp_seq=978 ttl=128 time=3000 ms > 64 bytes from 192.168.2.249: icmp_seq=979 ttl=128 time=2000 ms > 64 bytes from 192.168.2.249: icmp_seq=980 ttl=128 time=1000 ms > 64 bytes from 192.168.2.249: icmp_seq=981 ttl=128 time=4003 ms > 64 bytes from 192.168.2.249: icmp_seq=982 ttl=128 time=3001 ms > 64 bytes from 192.168.2.249: icmp_seq=983 ttl=128 time=4654 ms > 64 bytes from 192.168.2.249: icmp_seq=984 ttl=128 time=3654 ms > 64 bytes from 192.168.2.249: icmp_seq=985 ttl=128 time=2654 ms > > However, this is what happens :-( > > -----Mensagem original----- > De: dev [mailto:dev-bounces at dpdk.org] Em nome de Fred Pedrisa > Enviada em: quarta-feira, 26 de mar?o de 2014 20:34 > Para: dev at dpdk.org > Assunto: [dpdk-dev] l2fwd high latency/delay > > Hi, > > > > I am testing l2fwd in FreeBSD and I am noticing a delay of around 0~3 > seconds, what could be causing this behavior ? > > > > Fred > > >
