Meltdown – Spectre

Ralf Mardorf ralf.mardorf at
Tue Jan 9 00:20:39 UTC 2018

On Mon, 8 Jan 2018 19:58:21 +0100, Polytropon wrote:
>On Mon, 8 Jan 2018 09:57:56 +0100, Matthias Apitz wrote:
>> El día lunes, enero 08, 2018 a las 09:22:34a. m. +0100, Kristof
>> Provost escribió: 
>> > They have been aware of the problem for 6+ months. FreeBSD was
>> > notified in late December. It’s being worked on, but these are
>> > non-trivial changes, so it’ll take some time.  
>> As I side note, and not related to FreeBSD: My Internet server is
>> run by some webhosting company (, they use Ubuntu
>> servers and since yesterday they have shutdown SSH access to the
>> servers argumenting that they want protect my (all's) servers
>> against attacks of Meltdown and Spectre.
>> Imagine, next time we have to shutdown all IOT gadgets...  
>Additionally, prepare for your bills to increase. The current
>mitigation concepts, as far as I understand, result in a lower
>performance (about 20 %) of the patched (!) systems. So when
>you heavily rely on cloud infrastructures, and you have the
>magical "[x] upgrade my plan if justified by increased load"
>enabled, well... When things start costing money, you know
>who'll always pay... ;-)

"KPTI comes with a measurable run-time cost, estimated at about 5%.
That is a cost that some users may not want to pay, especially once
they get newer processors that lack these problems. There will be a
nopti command-line option to disable this mechanism at boot time." -

So for my audio workstation I much likely will boot with nopti and the
mentioned Ubuntu server seemingly slows down for around 5% and not
around 20% ;).


$ pacman -Q linux{,-rt{,-cornflower,-pussytoes}}|awk '{print $2}'

More information about the freebsd-questions mailing list