Date: Wed, 23 Nov 2022 08:13:27 -0500 From: mike tancsa <mike@sentex.net> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, Hans Petter Selasky <hps@selasky.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ULE realtime scheduler advice needed Message-ID: <1513f368-bdec-7c93-7c58-c23c5f594f01@sentex.net> In-Reply-To: <20221123070014.71f5cc4f1d86cb4d4c0f6bf6@dec.sakura.ne.jp> References: <7ad10a5e-29d6-aaef-25cf-407d65f056cc@selasky.org> <8d8c4b03-323a-8e4d-44fd-e47749d2fd85@sentex.net> <1a404155-4ca9-4e88-4c40-5407c2ae52a9@selasky.org> <20221123070014.71f5cc4f1d86cb4d4c0f6bf6@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/22/2022 5:00 PM, Tomoaki AOKI wrote:
> A long shot, but I am curious if by chance you have hwpstate_intel for
>>> your cpu frequency driver. If so, does setting
>>> dev.hwpstate_intel.0.epp=0 make any difference ?
>>>
>> Yes, I have four of those, set to 50 by default. Let me try.
>>
>> --HPS
> FYI: I habitally run below manually (as root) when I'm on AC powerline.
>
> sysctl -aN | fgrep dev.hwpstate | fgrep epp | while read OID ; do ; \
> sysctl ${OID}=0 ; done
It was a bit of a POLA the first time I encountered this driver going
from 12 to RELENG_13. Same hardware behaved rather differently as its a
different power profile default than what I expected and for my use case
(firewall and router) it was causing dropped packets
---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1513f368-bdec-7c93-7c58-c23c5f594f01>