Almost all of this was done within 24 hours of the last Lazy Reading. No idea why there were so many good candidates for reading, but I’m happy about it.
I’m still catching up with the pre-2018, pre-Meltdown commits, so here’s one: Changing the staged packet count in DragonFly changes forwarding rate, for the better – up to a point. There’s probably some specific ratio in the change that makes sense, though I don’t know it.
The Meltdown/Spectre talk continues on BSDNow 229, along with an interview of @newnix, GhostBSD, and other recent news.
The commands rcp(1), rlogin(1), rlogind(1), rsh(1) and rshd(1) have been removed from DragonFly. There’s a net/bsdrcmds port if you still need them… though I imagine/hope ssh is filling the void for everyone.
I’m sure this was needed by someone: morse(6) can now encode and decode Morse code, signified by . and – of course.
I say “one more” like I know when this saga will end. If you are using the devcpu-data port to update your processors, you’ll need to add
to your /etc/rc.conf, as Sepherosa Ziehau points out.
This is almost all link overflow from last week – and next week’s edition is almost complete. There’s a lot to read lately!
A full slate of BSDs this week.
The regular maintenance scripts for HAMMER1 assume that it’s mounted at the time of cleanup. If you have them unmounted, they won’t go through that regular maintenance, but it’s easy enough to fix.
Continuing the all-Spectre, all-Meltdown week here at the Digest, BSDNow 228 talks about it for FreeBSD and will cover more next week. And oh yeah other news, including a mention of new-to-me NomadBSD.
Matthew Dillon posted a summary of IBRS and IBPB support in DragonFly, and some numbers showing its impact in various configurations of options and CPUs.
Are you tired of hearing about Meltdown/Spectre yet? Doesn’t matter! The two sysctls for controlling mitigation in DragonFly have been renamed:
They go to hopefully sensible defaults, but Matthew Dillon has done some testing to show the effects of each in various combinations. (Update: more changes and tests.) Note that this is not the final mitigation work; compilers (i.e. gcc) are being updated to include workarounds for this, so new gcc -> new compiler in DragonFly -> new defenses. No silver bullet there, though.
One side effect of Meltdown/Spectre are CPU microcode (firmware) updates. For future needs: sysutils/devcpu-data is the port that has the updates for Intel, and cpucontrol(8) is the program you run on DragonFly to add them.
I haven’t used this myself, yet, so I can’t tell you how necessary an immediate update could be – but you will probably want to use it soon.
Update: Newer CPUs might require this sizing change.
Update update: a better explanation of applying microcode updates. There’s new ones out, too. (via)
If you’re on the bleeding edge of DragonFly and already updated for Meltdown fixes, there’s a few more commits you’ll want to get.
Update: step-by-step microcode fixes from Intel if you really want to trash your performance.
I had to trim this down; there’s been a post-Christmas surge in material.
Note the non-profit link; that may be useful to you.
I’m a bit late posting it, but: BSDNow 227 covers Open, Free, and Net this week.
By now you’ve probably heard of the Meltdown/Spectre attacks. (background rumors, technical note) Matthew Dillon’s put together a Meltdown mitigation in DragonFly, done in four commits.
It’s turned off and on by the sysctl machdep.isolated_user_pmap – and defaults to on for Intel CPUs. Buildworld tests show about a 4-5% performance hit, but that’s only one form of activity, measured, so there will surely be other effects.
Note that Spectre is not mitigated by this commit series, and as I understand it, cannot be realistically fixed in software.
Update: Matthew Dillon posted a summary to users@.
Update 2: He told us so.
A minor bit of housekeeping: the archives page has been fixed up to correctly list all categories, and list posts grouped by month. So if you want to see what I posted under the roguelike category, or see what I posted in February 2011, you can. Post counts provided, too.