From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by dpdk.org (Postfix) with ESMTP id ED5593F9 for ; Thu, 27 Mar 2014 03:16:42 +0100 (CET) Received: by mail-ob0-f169.google.com with SMTP id va2so3537219obc.14 for ; Wed, 26 Mar 2014 19:18:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=HP2Bm4FlDBt3c0UTBvvg7g6IgmfhMnKUfmOeZ3ES9lo=; b=ldRoAu+KrAIZxXDta/o5jNW1eTyMuE2tthaX9WBHYxaj+vVWY9xR4Xc6FB8GsZsiYN pktTMr+V9qh1ddK84cxZFPm8Tz1Xll1rEGqM69FdexSb2j44dKN0Q+2grawu5UT1/2n4 URTZe70g56of4EriOd9CJ7wajJAeIFdigibcCIqyNGhmV8HA8wRat+qaqG2rLd47gQTj h8hOhgzBlB7WGq0h4lrigEx0BPsIy0aJ0TOEipjHKcku6Pw0ElqTiS4QfyYNzNrzzNkm WjUFAieO8Y8aZYHxNr//sC864tJMlfNaGdtUpgdv08vGVFuSvlir3PofB+3FCGPQbfCn OExA== X-Gm-Message-State: ALoCoQmR7Hx/XjQrkWpr3t0JC46w5Owj3c05dWpT+QGUkyqpx3nNEwSPdQ1uBt8y/pLNpOGnE9y2 MIME-Version: 1.0 X-Received: by 10.60.55.97 with SMTP id r1mr11516663oep.5.1395886696159; Wed, 26 Mar 2014 19:18:16 -0700 (PDT) Received: by 10.182.24.198 with HTTP; Wed, 26 Mar 2014 19:18:16 -0700 (PDT) In-Reply-To: References: <028201cf494c$6405af30$2c110d90$@hotmail.com> Date: Thu, 27 Mar 2014 11:18:16 +0900 Message-ID: From: Masaru Oki To: Fred Pedrisa Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] 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:16:43 -0000 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 : > 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 > > >