DPDK usage discussions
 help / color / mirror / Atom feed
From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: AMD EPYC 7713 64-Core: cannot enable turbo boost
Date: Thu, 28 Apr 2022 10:05:48 +0200	[thread overview]
Message-ID: <CAO8pfFkiZGDN_LuSHi22PBn-2+99BOH+j99bi-KQUungLsbpqA@mail.gmail.com> (raw)
In-Reply-To: <CAO8pfFmzszNTxeoNjAYC55xtC=mqTKTBbFQr0qAppWLKDQFdTA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2402 bytes --]

Right now we are using an Intel XEON and to be able to enable turbo boost
we had to change a setting (Power performance tuning) in the BIOS sticking
it to "OS control EPB". Is there something to do in the BIOS of EPYC?



Il giorno mar 26 apr 2022 alle ore 18:25 Antonio Di Bacco <
a.dibacco.ks@gmail.com> ha scritto:

> That's fantastic:
>
> # sudo cpupower -c 99 frequency-info info
> analyzing CPU 99:
>   driver: acpi-cpufreq
>   CPUs which run at the same hardware frequency: 99
>   CPUs which need to have their frequency coordinated by software: 99
>   maximum transition latency:  Cannot determine or is not supported.
>   hardware limits: 1.50 GHz - 3.72 GHz
>   available frequency steps:  2.00 GHz, 1.70 GHz, 1.50 GHz
>   available cpufreq governors: conservative ondemand userspace powersave
> performance schedutil
>   current policy: frequency should be within 1.50 GHz and 3.72 GHz.
>                   The governor "userspace" may decide which speed to use
>                   within this range.
>   current CPU frequency: 2.00 GHz (asserted by call to hardware)
>   boost state support:
>     Supported: yes
>     Active: yes
>     Boost States: 0
>     Total States: 3
>     Pstate-P0:  2000MHz
>     Pstate-P1:  1700MHz
>     Pstate-P2:  1500MHz
>
> Il giorno mar 26 apr 2022 alle ore 12:00 Tummala, Sivaprasad <
> Sivaprasad.Tummala@amd.com> ha scritto:
>
>> [AMD Official Use Only - General]
>>
>>
>>
>> Hi Antonio,
>>
>>
>>
>> We are looking into this. Could you please share the below info:
>>
>> # cpupower -c <lcore> frequency-info info
>>
>> analyzing CPU <lcore>:
>>
>>   driver: acpi-cpufreq
>>
>>
>>
>>
>>
>> *From:* Antonio Di Bacco <a.dibacco.ks@gmail.com>
>> *Sent:* Monday, April 25, 2022 10:43 PM
>> *To:* users@dpdk.org
>> *Subject:* AMD EPYC 7713 64-Core: cannot enable turbo boost
>>
>>
>>
>> [CAUTION: External Email]
>>
>> Trying to enable turbo boost on EPYC 7713 with this APIS:
>>
>>
>>
>>   rte_power_init(lcore)
>>   rte_power_freq_enable_turbo(lcore)
>>  rte_power_freq_max(lcore)
>>
>>
>>
>>  I receive this messages:
>>
>>
>>
>> DPDK:POWER: Env isn't set yet!
>> DPDK:POWER: Attempting to initialise ACPI cpufreq power management...
>> DPDK:POWER: Power management governor of lcore 99 has been set to
>> 'userspace' successfully
>> DPDK:POWER: Initialized successfully for lcore 99 power management
>> DPDK:POWER: Failed to enable turbo on lcore 99
>>
>

[-- Attachment #2: Type: text/html, Size: 5071 bytes --]

      reply	other threads:[~2022-04-28  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 17:13 Antonio Di Bacco
2022-04-26 10:00 ` Tummala, Sivaprasad
2022-04-26 16:25   ` Antonio Di Bacco
2022-04-28  8:05     ` Antonio Di Bacco [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=CAO8pfFkiZGDN_LuSHi22PBn-2+99BOH+j99bi-KQUungLsbpqA@mail.gmail.com \
    --to=a.dibacco.ks@gmail.com \
    --cc=Sivaprasad.Tummala@amd.com \
    --cc=users@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).