Date: Wed, 5 May 2010 08:41:06 -0700 From: "Jack L." <xxjack12xx@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: Hubert Tournier <hubert@frbsd.org>, freebsd-smp@freebsd.org, oklahoma <stopeme@gmail.com> Subject: Re: Disabling HyperThreading? Message-ID: <p2yab581e311005050841ob19af115gca86fe06278796a@mail.gmail.com> In-Reply-To: <201004260948.12730.jhb@freebsd.org> References: <28357071.post@talk.nabble.com> <28359495.post@talk.nabble.com> <4BD563F7.4010203@googlemail.com> <201004260948.12730.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
sysctl machdep.hyperthreading_allowed=3D0 will disable it. On Mon, Apr 26, 2010 at 6:48 AM, John Baldwin <jhb@freebsd.org> wrote: > On Monday 26 April 2010 5:59:19 am oklahoma wrote: >> Hubert Tournier wrote: >> > >> > I forgot to specify that the system is a remote dedicated server, for > which >> > i have no physical access. >> > >> > I could rent a virtual KVM in order to try to access its BIOS settings= , > but >> > i'm not sure this would work. >> > >> > Any other software solution? >> if the server is dedicated entirely to you, ask your colo support to >> disable it for you. >> other thing i find was >> >> machdep.hlt_cpus >> >> is suppose to tell the scheduler that there is extra cores but not to us= e > them. >> try to enable and see with top is there app that use logical cores. > > You can manually disable any CPU (except for the boot CPU), via > 'hint.lapic.X.disabled=3D1' in loader.conf. =C2=A0You can find the APIC I= Ds to use in > place of 'X' in dmesg. > > -- > John Baldwin > _______________________________________________ > freebsd-smp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-smp > To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p2yab581e311005050841ob19af115gca86fe06278796a>