Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Nov 2007 09:13:29 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        brde@optusnet.com.au
Cc:        sobomax@FreeBSD.ORG, src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, kris@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cperciva@FreeBSD.ORG, nate@root.org
Subject:   Re: cvs commit: src/sys/amd64/amd64 mp_machdep.c src/sys/i386/i386 mp_machdep.c
Message-ID:  <20071110.091329.-894584211.imp@bsdimp.com>
In-Reply-To: <20071110190555.I35816@delplex.bde.org>
References:  <4734B13C.6050008@root.org> <4735008D.7030600@FreeBSD.org> <20071110190555.I35816@delplex.bde.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20071110190555.I35816@delplex.bde.org>
            Bruce Evans <brde@optusnet.com.au> writes:
: On Fri, 9 Nov 2007, Maxim Sobolev wrote:
: 
: > For what it is worth I think Nate has the correct point. We should not force 
: > this setting upon each and every user if it can realistically affect only 
: > 0.0001% of our userbase. Leaving this setting on for production server that 
: > does lot of sensitive crypto and has lot of untrusted remote users is like 
: > leaving open access to the server console in the common room. At the same 
: > time, most of us have open access to consoles of their laptops/desktops at 
: > home/work.
: 
: Nothing is forced, since the setting is only the default.
: 
: Off is a good default since hyperthreading seems to be a pessimization
: in most casts.

hyperthreading for mysql using ULE is a big gain.  What workloads is
it a pessimization?

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071110.091329.-894584211.imp>