Date: Wed, 21 Sep 2022 22:15:21 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Paul Procacci <pprocacci@gmail.com> Cc: "freebsd-questions@freebsd.org" <questions@freebsd.org> Subject: Re: Disabling CPUs Message-ID: <CAN6yY1sqwFQ1EkaV5PBNU7uOMuZoi90=FBvLjVaOuXpmwM00ow@mail.gmail.com> In-Reply-To: <CAFbbPuijZ9YmRkS=0JdHNNj34Zv8Qoh78nbnP2JbHCyotD-fiA@mail.gmail.com> References: <CAN6yY1s=ds_=yWsEWtVfoXchD5XXqU5uPw6bdFNW%2BdaU6t491A@mail.gmail.com> <CAFbbPuijZ9YmRkS=0JdHNNj34Zv8Qoh78nbnP2JbHCyotD-fiA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Wed, Sep 21, 2022 at 7:26 PM Paul Procacci <pprocacci@gmail.com> wrote:
> (Resending with list included)
>
> Hey Keith,
>
> Taken from smp(4):
>
> FreeBSD allows specific CPUs on a multi-processor system to be
> disabled.
> This can be done using the hint.lapic.X.disabled tunable, where X is
> the
> APIC ID of a CPU. Setting this tunable to 1 will result in the
> corresponding CPU being disabled.
>
> smp(4) further describes how to detect CPU topologies and whatnot.
> Specifically the following sysctl seems useful: kern.sched.topology_spec
>
> Though I'm not entirely sure, I'd personally start with the above.
>
> ~Paul
>
> On Wed, Sep 21, 2022 at 10:06 PM Kevin Oberman <rkoberman@gmail.com>
> wrote:
>
>> I am looking to disable all 8 E-cores on my Alder Lake system to prevent
>> repeated crashes. The man page has an example of this:
>> Modify the cpuset all threads are in by default to contain only the first
>> 4 CPUs, leaving the rest idle:
>> cpuset -l 0-3 -s 1
>> I did this, but in subsequent port build, all 12 "CPUs" were running at
>> 100%. Am I missing something? Maybe use -p 1" instead of "-s 1".
>>
>> I also found suggestions to use "hint.lapic.N.disabled", but teh lines
>> that were supposed to be in dmesg and the messages log were not present. I
>> am baffled, but really need to do something to stop the crashes currently
>> impacting Alder Lake systems.
>> --
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkoberman@gmail.com
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>
>
>
> --
> __________________
>
> :(){ :|:& };:
>
Nothing looks useful in kern.sched. I am wondering if SCHED_4BSD is
impacting this. My knowledge of the schedulers is minimal, but 4BSD
provided much better responsiveness than ULE.I 've been running 4BSD on my
systems (excluding servers) for over a decade... Probably much longer. I
may try building a kernel with ULE and see what effect that has.
# sysctl kern.sched
kern.sched.runq_fuzz: 1
kern.sched.ipiwakeup.useloop: 0
kern.sched.ipiwakeup.usemask: 1
kern.sched.ipiwakeup.delivered: 26954287
kern.sched.ipiwakeup.requested: 26899799
kern.sched.ipiwakeup.enabled: 1
kern.sched.slice: 12
kern.sched.quantum: 94488
kern.sched.name: 4BSD
kern.sched.preemption: 1
kern.sched.cpusetsize: 32
-
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">On Wed, Sep 21, 2022 at 7:26 PM Paul Procacci <<a href="mailto:pprocacci@gmail.com">pprocacci@gmail.com</a>> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">
<div>(Resending with list included)<br><br>Hey Keith,</div><div><br></div><div>Taken from smp(4):<br><br></div><div> FreeBSD allows specific CPUs on a multi-processor system to be disabled.<br> This can be done using the hint.lapic.X.disabled tunable, where X is the<br> APIC ID of a CPU. Setting this tunable to 1 will result in the<br> corresponding CPU being disabled.<br><br></div><div>smp(4) further describes how to detect CPU topologies and whatnot.<br></div><div>Specifically the following sysctl seems useful: kern.sched.topology_spec<br></div><div><br></div><div>Though I'm not entirely sure, I'd personally start with the above.<font color="#888888"><br><br></font></div><font color="#888888"><div>~Paul</div></font>
</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 21, 2022 at 10:06 PM Kevin Oberman <<a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small">I am looking to disable all 8 E-cores on my Alder Lake system to prevent repeated crashes. The man page has an example of this:</div><div style="font-family:tahoma,sans-serif;font-size:small">Modify the cpuset all threads are in by default to contain only the first 4 CPUs, leaving the rest idle:<br> cpuset -l 0-3 -s 1</div><div style="font-family:tahoma,sans-serif;font-size:small">I did this, but in subsequent port build, all 12 "CPUs" were running at 100%. Am I missing something? Maybe use -p 1" instead of "-s 1".</div><div style="font-family:tahoma,sans-serif;font-size:small"><br></div><div style="font-family:tahoma,sans-serif;font-size:small">I also found suggestions to use "hint.lapic.N.disabled", but teh lines that were supposed to be in dmesg and the messages log were not present. I am baffled, but really need to do something to stop the crashes currently impacting Alder Lake systems.<br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr">__________________<br><br>:(){ :|:& };:</div>
</blockquote></div><br clear="all"><br><div><br></div><div><span class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Nothing looks useful in kern.sched. I am wondering if SCHED_4BSD is impacting this. My knowledge of the schedulers is minimal, but 4BSD provided much better responsiveness than ULE.I 've been running 4BSD on my systems (excluding servers) for over a decade... Probably much longer. I may try building a kernel with ULE and see what effect that has.<br></span></div><div><span class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></span></div><div><span class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"></span># sysctl kern.sched</div>kern.sched.runq_fuzz: 1<br>kern.sched.ipiwakeup.useloop: 0<br>kern.sched.ipiwakeup.usemask: 1<br>kern.sched.ipiwakeup.delivered: 26954287<br>kern.sched.ipiwakeup.requested: 26899799<br>kern.sched.ipiwakeup.enabled: 1<br>kern.sched.slice: 12<br>kern.sched.quantum: 94488<br><a href="http://kern.sched.name">kern.sched.name</a>: 4BSD<br>kern.sched.preemption: 1<br>kern.sched.cpusetsize: 32<br>- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sqwFQ1EkaV5PBNU7uOMuZoi90=FBvLjVaOuXpmwM00ow>