From: "Liang, Cunming" <cunming.liang@intel.com>
To: Victor Detoni <victordetoni@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] l2fwd consumes 100% cpu
Date: Mon, 8 Jun 2015 06:52:48 +0000 [thread overview]
Message-ID: <D0158A423229094DA7ABF71CF2FA0DA3119694DC@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CANpwN=sjwCxKGRwQrT-hW44Jat28worHbhJzpwVQGJjVJg9iwg@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Victor Detoni
> Sent: Monday, June 08, 2015 9:06 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] l2fwd consumes 100% cpu
>
> hello,
>
> I'm looking for some documentation about this issue, but I could found yet.
> So, I would like to know if there is some resource like a poll or select to
> put on l2fwd_main_loop?
The way to limit the cpu utilization is set a specific quota for your thread by cgroup.
If you do like to sleep your thread when there's no traffic.
There's a patch set to enable thread wait-up from epoll_wait by one shot rx interrupt.
http://article.gmane.org/gmane.comp.networking.dpdk.devel/18942
>
> It would be great to analyse cpu consumption, because I can see 100% of cpu
> with no traffic pass through it.
>
> thanks
> Victor
prev parent reply other threads:[~2015-06-08 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 1:05 Victor Detoni
2015-06-08 6:52 ` Liang, Cunming [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=D0158A423229094DA7ABF71CF2FA0DA3119694DC@shsmsx102.ccr.corp.intel.com \
--to=cunming.liang@intel.com \
--cc=dev@dpdk.org \
--cc=victordetoni@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).