From: Fred Pedrisa <fredhps10@hotmail.com>
To: "'Vladimir Medvedkin'" <medvedkinv@gmail.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] RES: L2FWD uses 'too much' CPU
Date: Tue, 1 Apr 2014 13:43:14 -0300 [thread overview]
Message-ID: <COL131-DS23319B3CEC539CB7656CA0B0620@phx.gbl> (raw)
In-Reply-To: <067001cf4dc8$b18539d0$148fad70$@gmail.com>
Hello,
Ok. Can you help me with something else ?
Right now, at a rate of 1.3~1.4 Mpps I am having about 4~5% of packet loss,
I wonder if I use my application wth a 10G NIC, will it not be able to cope
with more than 1.4 Mpps ? Because by seeing a packet loss I got a little
afraid of it.
Sincerely,
Fred
De: Vladimir Medvedkin [mailto:medvedkinv@gmail.com]
Enviada em: terça-feira, 1 de abril de 2014 13:36
Para: Fred Pedrisa
Cc: dev@dpdk.org
Assunto: Re: [dpdk-dev] L2FWD uses 'too much' CPU
Hi,
One of the objectives of DPDK is avoiding of interrupts, so application (not
only L2FWD) polls NIC infineteley. You can look at programmers guide
section 24 "Power Management" and "L3 Forwarding with Power Management
Sample Application" in Sample Applications User Guide.
Regards,
Vladimir.
2014-04-01 9:24 GMT+04:00 Fred Pedrisa <fredhps10@hotmail.com>:
Hi,
Why by default L2FWD saturate both cores ? I mean, it seems it keeps wasting
cycles due to the infinite loop placed there to check the queues.
Which would be the way to improve this and make it to become more efficient
?
Sincerely,
Fred
prev parent reply other threads:[~2014-04-01 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 5:24 [dpdk-dev] " Fred Pedrisa
2014-04-01 16:36 ` Vladimir Medvedkin
[not found] ` <067001cf4dc8$b18539d0$148fad70$@gmail.com>
2014-04-01 16:43 ` Fred Pedrisa [this message]
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-DS23319B3CEC539CB7656CA0B0620@phx.gbl \
--to=fredhps10@hotmail.com \
--cc=dev@dpdk.org \
--cc=medvedkinv@gmail.com \
/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).