Re: Hyperthreading not disabled on E5-2690 v1?

[Peter Kay]

Yep, I looked at the Top source after that and saw that the inactive
CPU hiding code was backed out seven days ago.

Running a make -j32 on a port shows that only CPUs 0-15 are active. Cheers!

PK
On Fri, 12 Oct 2018 at 21:41, Stuart Henderson  wrote:
>
> On 2018-10-12, Peter Kay  wrote:
> > I can't see any recent source code changes about hyperthreading, and
> > presume it's still supposed to be disabled by default?
> >
> > It is not disabled on an EP2C602 with two E5-2690 CPUs (Sandy Bridge
> > EP), I can see 32 'CPUs' in both top and systat.
> >
> > Bug I presume..? Can provide dmesg, debugging info, and remote access
> > if necessary.
> >
> > hw.smt is set to zero
> >
> > PK
> >
> >
>
> Currently I would expect them to show up but not have processes
> scheduled to them.
>
>

Re: Hyperthreading not disabled on E5-2690 v1?

[Stuart Henderson]

On 2018-10-12, Peter Kay  wrote:
> I can't see any recent source code changes about hyperthreading, and
> presume it's still supposed to be disabled by default?
>
> It is not disabled on an EP2C602 with two E5-2690 CPUs (Sandy Bridge
> EP), I can see 32 'CPUs' in both top and systat.
>
> Bug I presume..? Can provide dmesg, debugging info, and remote access
> if necessary.
>
> hw.smt is set to zero
>
> PK
>
>

Currently I would expect them to show up but not have processes
scheduled to them.

Hyperthreading not disabled on E5-2690 v1?

[Peter Kay]

I can't see any recent source code changes about hyperthreading, and
presume it's still supposed to be disabled by default?

It is not disabled on an EP2C602 with two E5-2690 CPUs (Sandy Bridge
EP), I can see 32 'CPUs' in both top and systat.

Bug I presume..? Can provide dmesg, debugging info, and remote access
if necessary.

hw.smt is set to zero

PK