From: Fred Pedrisa <fredhps10@hotmail.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] RES: l2fwd high latency/delay
Date: Wed, 26 Mar 2014 21:56:13 -0300 [thread overview]
Message-ID: <COL131-DS37F10BDDA3E2553BEF561B0670@phx.gbl> (raw)
In-Reply-To: <028201cf494c$6405af30$2c110d90$@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@dpdk.org] Em nome de Fred Pedrisa
Enviada em: quarta-feira, 26 de março 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
next parent reply other threads:[~2014-03-27 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <028201cf494c$6405af30$2c110d90$@hotmail.com>
2014-03-27 0:56 ` Fred Pedrisa [this message]
2014-03-27 2:18 ` Masaru Oki
[not found] ` <029601cf4963$050e58d0$0f2b0a70$@stratosphere.co.jp>
2014-03-27 2:26 ` [dpdk-dev] RES: " Fred Pedrisa
[not found] ` <02a601cf4964$598eed10$0cacc730$@hotmail.com>
2014-03-27 2:54 ` [dpdk-dev] RES: " Fred Pedrisa
[not found] ` <02b901cf4968$1646f850$42d4e8f0$@hotmail.com>
2014-03-27 4:59 ` [dpdk-dev] RES: " Fred Pedrisa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=COL131-DS37F10BDDA3E2553BEF561B0670@phx.gbl \
--to=fredhps10@hotmail.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).