From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 29219A034C for ; Thu, 28 Apr 2022 10:06:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A8628410E1; Thu, 28 Apr 2022 10:06:02 +0200 (CEST) Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) by mails.dpdk.org (Postfix) with ESMTP id E422E410DC for ; Thu, 28 Apr 2022 10:06:00 +0200 (CEST) Received: by mail-lj1-f172.google.com with SMTP id y19so5668646ljd.4 for ; Thu, 28 Apr 2022 01:06:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jAWKkKagTPO70EafwPl/yr/chqibkiwaekJOMIEWCW4=; b=oPsRpkmkSmxYTiYuHt9CoN4ap/iy8qVcsz9KOKObIQDv2JYa1ZIlH9/pluB+O+8sRa 19yQxB8t8Rk+5Jozxq9K7Z4CmKLhXbZ2ywkuQJRmhvwc2k3cpkY8dq/VYWBVPQeLTE12 naC2bjnVCeFLB1QB0htyBaW21OozrpqQz7l81/XhW89uTdQcnVz8BZkYYF+jmG4gZrl3 lJb1Ez1DAFojC9oTss0cYlXVNlvn5d4VCPCkbnGOXibljNLfY567dWHzisOhg/lVhwqh JY0DXQY7ul7rhXwrvSct/LG1soyCn2v8C4ZT9MZWdTRtJ88LgmSYmQNvuUj+sj1n6uVX iABA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jAWKkKagTPO70EafwPl/yr/chqibkiwaekJOMIEWCW4=; b=yoGtGeMAkDaR69Po8AT+EsU3EZM65WquQCQ1i7bnL4cQcceJRQlKxKLAWWUUp7AbOz Kk+sAS+kMsHt2xi+WNm8RDyUIYUkYQU5ecKQeQqQ4vbtdU9Va49IKApO+hfp4P/8foiR mhFkA7TlJWsBr1D0KZN9GdUHAdT7jv7bvzkRQrx7Q+CGBNH2K6kjo8koZ+GtEw/joEr+ yvtTdDW1CvxKtGP6/3xM7T91CVQdHcc2WPKF+l8JQv3roAEj8a0JVnTXABMGIxU4frjB F32P0hUNI8qbTr5i0/Q4y+JvayWbqO/EN5XxEQ4lqY9a0MOi8G/C/li0zRNMDUSpoWXp 2QaQ== X-Gm-Message-State: AOAM53371hvoBREcBMFlPklvz09OrxPWD56ws5sT85Jd2wmSo2/aaMkG PVz+dqrEqgEiJtLpxsBbYVXI3VyeTD7T1BL1kCI= X-Google-Smtp-Source: ABdhPJwZdpUU43NyUVDPYib6V9Kieg1qgdf98rrd6BzQjzde2IVkUWM6koXxhALY1GwFk6JgE3XLZILRkUt0XGF6EZA= X-Received: by 2002:a2e:8557:0:b0:24f:f3d:c526 with SMTP id u23-20020a2e8557000000b0024f0f3dc526mr13239600ljj.350.1651133160102; Thu, 28 Apr 2022 01:06:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Antonio Di Bacco Date: Thu, 28 Apr 2022 10:05:48 +0200 Message-ID: Subject: Re: AMD EPYC 7713 64-Core: cannot enable turbo boost To: "Tummala, Sivaprasad" Cc: "users@dpdk.org" Content-Type: multipart/alternative; boundary="0000000000007c1cc605ddb26526" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --0000000000007c1cc605ddb26526 Content-Type: text/plain; charset="UTF-8" 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 frequency-info info >> >> analyzing CPU : >> >> driver: acpi-cpufreq >> >> >> >> >> >> *From:* Antonio Di Bacco >> *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 >> > --0000000000007c1cc605ddb26526 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Right now we are using an Intel XEON and to be able to ena= ble turbo boost we had to change a setting (Power performance tuning) in th= e 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:
=C2=A0 driver: acpi-cpufreq
=C2=A0 CPUs which run at the same har= dware frequency: 99
=C2=A0 CPUs which need to have their frequency coord= inated by software: 99
=C2=A0 maximum transition latency: =C2=A0Cannot d= etermine or is not supported.
=C2=A0 hardware limits: 1.50 GHz - 3.72 GH= z
=C2=A0 available frequency steps: =C2=A02.00 GHz, 1.70 GHz, 1.50 GHz=C2=A0 available cpufreq governors: conservative ondemand userspace power= save performance schedutil
=C2=A0 current policy: frequency should be wi= thin 1.50 GHz and 3.72 GHz.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 The governor "userspace" may decide which sp= eed to use
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 within this range.
=C2=A0 current CPU frequency: 2.00 GHz (asserted = by call to hardware)
=C2=A0 boost state support:
=C2=A0 =C2=A0 Suppor= ted: yes
=C2=A0 =C2=A0 Active: yes
=C2=A0 =C2=A0 Boost States: 0
= =C2=A0 =C2=A0 Total States: 3
=C2=A0 =C2=A0 Pstate-P0: =C2=A02000MHz
= =C2=A0 =C2=A0 Pstate-P1: =C2=A01700MHz
=C2=A0 =C2=A0 Pstate-P2: =C2=A015= 00MHz

Il giorno mar 26 apr 2022 alle ore 12:00 Tummala, Sivaprasa= d <Sivap= rasad.Tummala@amd.com> ha scritto:

[AMD Official Use Only - General]<= /p>

=C2=A0

Hi Antonio,

=C2=A0

We are looking into this. Could you please share the below info:

# cpupower -c <lcore> frequency-info info

analyzing CPU <lcore>:

=C2=A0 driver: acpi-cpufreq

=C2=A0

=C2=A0

From: Antonio Di Bacco <a.dibacco.ks@gmail.com> Sent: Monday, April 25, 2022 10:43 PM
To: users@dpdk.o= rg
Subject: AMD EPYC 7713 64-Core: cannot enable turbo boost<= /u>

=C2=A0

[CAUTION: External Email]

Trying to enable turbo boost on EPYC 7713 with this = APIS:

=C2=A0

=C2=A0 rte_power_init(lcore)
=C2=A0 rte_power_freq_enable_turbo(lcore)
=C2=A0rte_power_freq_max(lcore)

=C2=A0

=C2=A0I receive this messages:

=C2=A0

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 'user= space' successfully
DPDK:POWER: Initialized successfully for lcore 99 power management
DPDK:POWER: Failed to enable turbo on lcore 99

--0000000000007c1cc605ddb26526--