From: Stephen Hemminger <stephen@networkplumber.org>
To: Aaron Campbell <aaron@arbor.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Polling too often at lower packet rates?
Date: Thu, 9 Apr 2015 14:24:37 -0700 [thread overview]
Message-ID: <20150409142437.203fed44@urahara> (raw)
In-Reply-To: <16D8F22D-333F-499F-8B5A-4839E582054D@arbor.net>
On Thu, 9 Apr 2015 15:26:23 -0300
Aaron Campbell <aaron@arbor.net> wrote:
> Hi Stephen,
>
> Thanks, that was an informative talk. In this case, are you referring to your comments about the thermal budget?
>
> That’s definitely interesting, but there must be more to it than that. Again, if I loop over all 6 ports (i.e., continue to keep the CPU busy), it works around the problem.
>
> I agree that adaptive polling makes sense and will look into it. But will still take any further ideas on what is going on here.
>
> -Aaron
Your excess polling consumes PCI bandwidth which is a fixed resource.
next prev parent reply other threads:[~2015-04-09 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 16:35 Aaron Campbell
2015-04-08 18:00 ` Stephen Hemminger
2015-04-09 18:26 ` Aaron Campbell
2015-04-09 21:24 ` Stephen Hemminger [this message]
2015-04-10 0:42 ` Paul Emmerich
2015-04-10 1:05 ` Paul Emmerich
2015-04-08 19:11 ` Ananyev, Konstantin
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=20150409142437.203fed44@urahara \
--to=stephen@networkplumber.org \
--cc=aaron@arbor.net \
--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).