From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from col0-omc4-s4.col0.hotmail.com (col0-omc4-s4.col0.hotmail.com [65.55.34.206]) by dpdk.org (Postfix) with ESMTP id 186943F9 for ; Thu, 27 Mar 2014 03:53:18 +0100 (CET) Received: from COL131-DS12 ([65.55.34.200]) by col0-omc4-s4.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 Mar 2014 19:54:51 -0700 X-TMN: [EFKWv+uS0P0XzMKrGTqGMaXk3NSlXde7Ma36qJHEt74=] X-Originating-Email: [fredhps10@hotmail.com] Message-ID: From: Fred Pedrisa To: "'Masaru Oki'" References: <028201cf494c$6405af30$2c110d90$@hotmail.com> <029601cf4963$050e58d0$0f2b0a70$@stratosphere.co.jp> <02a601cf4964$598eed10$0cacc730$@hotmail.com> In-Reply-To: <02a601cf4964$598eed10$0cacc730$@hotmail.com> Date: Wed, 26 Mar 2014 23:54:56 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIRpb+NHtUUDfWX9lmK8sREX8OxtwFFltjaAfHDS+sCJFCEMppEpvsQ Content-Language: pt-br X-OriginalArrivalTime: 27 Mar 2014 02:54:51.0608 (UTC) FILETIME=[EC8BD580:01CF4967] Cc: dev@dpdk.org Subject: [dpdk-dev] RES: RES: RES: l2fwd high latency/delay X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2014 02:53:19 -0000 Hello, Also the same problem happens with : testpmd 64 bytes from 192.168.2.81: icmp_seq=3D1612 ttl=3D64 time=3D1002.400 ms 64 bytes from 192.168.2.81: icmp_seq=3D1613 ttl=3D64 time=3D2833.217 ms 64 bytes from 192.168.2.81: icmp_seq=3D1614 ttl=3D64 time=3D1832.221 ms 64 bytes from 192.168.2.81: icmp_seq=3D1615 ttl=3D64 time=3D4004.454 ms 64 bytes from 192.168.2.81: icmp_seq=3D1616 ttl=3D64 time=3D3003.457 ms 64 bytes from 192.168.2.81: icmp_seq=3D1617 ttl=3D64 time=3D2002.460 ms 64 bytes from 192.168.2.81: icmp_seq=3D1618 ttl=3D64 time=3D3526.880 ms 64 bytes from 192.168.2.81: icmp_seq=3D1619 ttl=3D64 time=3D2525.883 ms 64 bytes from 192.168.2.81: icmp_seq=3D1620 ttl=3D64 time=3D1524.885 ms 64 bytes from 192.168.2.81: icmp_seq=3D1621 ttl=3D64 time=3D2576.861 ms 64 bytes from 192.168.2.81: icmp_seq=3D1622 ttl=3D64 time=3D1575.864 ms 64 bytes from 192.168.2.81: icmp_seq=3D1623 ttl=3D64 time=3D574.866 ms -----Mensagem original----- De: dev [mailto:dev-bounces@dpdk.org] Em nome de Fred Pedrisa Enviada em: quarta-feira, 26 de mar=E7o de 2014 23:27 Para: 'Masaru Oki' Cc: dev@dpdk.org Assunto: [dpdk-dev] RES: RES: l2fwd high latency/delay Hello, =20 I see, but even making it=92s value as 1, still doesn=92t help ? :/ =20 De: Masaru Oki [mailto:m-oki@stratosphere.co.jp] Enviada em: = quarta-feira, 26 de mar=E7o de 2014 23:18 Para: Fred Pedrisa Cc: dev@dpdk.org Assunto: Re: [dpdk-dev] RES: l2fwd high latency/delay =20 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. =20 2014-03-27 9:56 GMT+09:00 Fred Pedrisa : 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=3D967 ttl=3D128 time=3D1630 ms 64 bytes from 192.168.2.249: icmp_seq=3D968 ttl=3D128 time=3D5005 ms 64 bytes from 192.168.2.249: icmp_seq=3D969 ttl=3D128 time=3D4004 ms 64 bytes from 192.168.2.249: icmp_seq=3D970 ttl=3D128 time=3D3003 ms 64 bytes from 192.168.2.249: icmp_seq=3D971 ttl=3D128 time=3D3661 ms 64 bytes from 192.168.2.249: icmp_seq=3D972 ttl=3D128 time=3D2660 ms 64 bytes from 192.168.2.249: icmp_seq=3D973 ttl=3D128 time=3D1660 ms 64 bytes from 192.168.2.249: icmp_seq=3D974 ttl=3D128 time=3D3001 ms 64 bytes from 192.168.2.249: icmp_seq=3D975 ttl=3D128 time=3D2001 ms 64 bytes from 192.168.2.249: icmp_seq=3D976 ttl=3D128 time=3D1000 ms 64 bytes from 192.168.2.249: icmp_seq=3D977 ttl=3D128 time=3D0.713 ms 64 bytes from 192.168.2.249: icmp_seq=3D978 ttl=3D128 time=3D3000 ms 64 bytes from 192.168.2.249: icmp_seq=3D979 ttl=3D128 time=3D2000 ms 64 bytes from 192.168.2.249: icmp_seq=3D980 ttl=3D128 time=3D1000 ms 64 bytes from 192.168.2.249: icmp_seq=3D981 ttl=3D128 time=3D4003 ms 64 bytes from 192.168.2.249: icmp_seq=3D982 ttl=3D128 time=3D3001 ms 64 bytes from 192.168.2.249: icmp_seq=3D983 ttl=3D128 time=3D4654 ms 64 bytes from 192.168.2.249: icmp_seq=3D984 ttl=3D128 time=3D3654 ms 64 bytes from 192.168.2.249: icmp_seq=3D985 ttl=3D128 time=3D2654 ms However, this is what happens :-( -----Mensagem original----- De: dev [mailto:dev-bounces@dpdk.org] Em nome de Fred Pedrisa Enviada = em: quarta-feira, 26 de mar=E7o de 2014 20:34 Para: dev@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 =20