From: Threqn Peng <phyorat@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] librte_power w/ intel_pstate cpufreq governor
Date: Wed, 1 Mar 2017 17:22:30 +0800 [thread overview]
Message-ID: <CACPQs+pzGFCHCB4e-U38me-7NhXge5-a3WyUVBgt=_3k0aR0Kg@mail.gmail.com> (raw)
In-Reply-To: <CACPQs+pvcZrH=1ND+7Yx-=cqSpJ78aKy65-Gexikn+ta8LfjPQ@mail.gmail.com>
Hello,
The solution should be "rte_epoll_wait". 10G NIC burst handling with in
"rte_epoll_wait" state(rx-queue number:12), pkt loss rate is about 0.003%.
Patch mail list(http://dpdk.org/ml/archives/dev/2015-February/014191.html)
As for "cpu scaling frequence", I think the better choice should be
leaving it to P-State, since driver-controlling is better than user's
acknowledgement of hardware state.
FYI.
Best Regards,
Peng
On 27 February 2017 at 13:56, Threqn Peng <phyorat@gmail.com> wrote:
> Hey guys,
>
> I have the same problem which have been discussed in January 2016(*http://dpdk.org/ml/archives/dev/2016-January/031374.html
> <http://dpdk.org/ml/archives/dev/2016-January/031374.html>*), about intel
> cpu scaling frequency control in linux user space. But it seems no more
> progress/solution relate to this problem until now.
>
> I also checked the example code:"L3 Forwarding with Power Management
> Sample Application" in newest dpdk version (17.02) , no update yet.
>
> Is it true that, newer cpufreq driver p-state only support two
> control-mode: "performance" and "powersave", and we can't do any more about
> cpu working frequency control, for power-saving?
>
> Thanks for your help.
>
> Best Regards,
> Peng
>
next prev parent reply other threads:[~2017-03-01 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 5:56 Threqn Peng
2017-03-01 9:22 ` Threqn Peng [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-02 7:18 longtb5
2018-03-02 7:20 ` longtb5
2018-03-05 10:16 ` Hunt, David
2018-03-05 10:48 ` longtb5
2018-03-05 11:25 ` Hunt, David
2018-03-05 12:23 ` longtb5
2015-12-06 0:08 Matthew Hall
2016-01-03 7:51 ` Matthew Hall
2016-01-12 15:17 ` Zhang, Helin
2016-01-14 7:03 ` Matthew Hall
2016-01-14 7:11 ` Matthew Hall
2016-01-14 7:15 ` Zhang, Helin
2016-01-14 7:44 ` Matthew Hall
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='CACPQs+pzGFCHCB4e-U38me-7NhXge5-a3WyUVBgt=_3k0aR0Kg@mail.gmail.com' \
--to=phyorat@gmail.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).