You can make them, but you can’t mount them. Tomohiro Kusumi’s note that mkfs_hammer2 works on Linux is of little wide practical use, but it’s a sign of progress to a larger goal.
I should have linked this with yesterday’s post: Sepherosa Ziehau put together some extended benchmarks on his changes between DragonFly 4.8 and 5.0, and their effects on latency using nginx to serve a lot of requests.
An optimization that applies to you only if you are on DragonFly, running nginx, and dealing with many requests: there’s a sysctl that specifically increases available sockets, which will decrease latency; Sepherosa Ziehau’s commit message gives stats.
SSH in DragonFly 5, by default, does not make a password authentication request on outgoing ssh sessions. You can manually add the option or change the config. Or use public keys, which is really the best idea if at all possible.
DragonFly has also gained the vmx(4) virtual network driver. This is in DragonFly-current now and will be in the 5.0 release.
kcollect(8) (see previous mention) now supports saving data to dbm files, thanks to Harald Brinkhof.
In addition to the already-mentioned ipfw per-CPU state tracking, Sepherosa Ziehau has added per-CPU state tables to ipfw, and his commit documents the improvement in performance/latency. He’s also added ipfw support to sshlockout(8).
Sepherosa Ziehau has made some improvements to ipfw in DragonFly, moving it to per-CPU state tracking among other things. (I haven’t mentioned just ipfw in foreeeever.)
His commit message describes the improvements. Of most interest: it reduces the performance impact of running ipfw in his tests to almost nothing. Does this translate to ipfw on other BSDs? I don’t know.
“gee, we have a 6-digit PID, might as well make it work to a million!”
Here’s the first of several commits to support this, and here’s the highest load averages I’ve ever seen.
There’s a new facility in DragonFly: kcollect(8). It holds automatically-collected kernel data for about the last day, and can output to gnuplot. Note the automatic collection part; your system will always be able to tell you about weirdness – assuming that weirdness extends to one of the features kcollect tracks. Here’s some of the commits.
Matthew Dillon’s found a solution to the problem of hardlinks in HAMMER2, and so moved on to dirents. The design document has a significant update to match.
sshlockout(8) will now lock out based on number of attempts, just so that you don’t have huge logs of stubborn but stupid SSH brute force attacks.
If you’ve had odd behavior with node.js (which I have) on DragonFly, it may be fixed now.
Sascha Wildner has updated ACPICA in DragonFly to Intel’s version 20170629. This will be of most interest to those with newer motherboards, as it matches ACPI 6.2.
A recent commit from Matthew Dillon serves as a rough safety valve, making it harder to fork/chroot yourself to death.
Apparently there’s a missing dhclient feature in DragonFly needed to run on OpenStack. Matthew Dillon’s made a change to get it to work – though I can’t find the exact commit.
Version 1.13.1 of nginx now natively uses CPU affinity on DragonFly. This matches well with SO_REUSEPORT support; I suspect DragonFly is a fantastic place to run nginx at this point.
…And before you say, “It would be great if someone would put together benchmarks”, think instead, “I’m someone, and I could do it.”
Imre Vadasz added support for ADMA2 transfers in DragonFly. It doesn’t lead to a huge performance boost – yet. It can be turned on and off, but requires Intel chipsets.
Francois Tigeot has brought in the ‘apple_gmux’ driver. If you have a Macbook with both Intel and NVIDIA video hardware installed, this driver lets you switch to the Intel hardware, and I assume take advantage of DragonFly’s accelerated i915 driver.