Alex Hornung has added the basic work for dmirror, a software RAID-1 implementation into the tree, along with a concept description from Matthew Dillon. It’s not ready for use yet; ready for development, though.
APIC_IO is back as a kernel config option, though it just toggles the sysctl loader tunable default. This is so a kernel config file with that option still set won’t cause an error.
Peter Avalos has committed his speedups for OpenSSL encryption (using assembly), along with a lot of numbers to show performance changes. It’s definitely sped up, but the quantity of values is so large that you’d have to visualize it differently to get a summary I could show here.
Peter Avalos is bringing in OpenSSL 1.0.0b. I’m not sure what the difference between 1.0.0b and 1.0.1 would be. Also, Alex Hornung has updated vn(4) – there’s more updates than the one I linked.
Ilya Dryomov’s work on deduplication for Hammer has been committed to the tree in an early test form. I guess I need to pay up as part of the code bounty. If you’re wondering how much space it will save, but don’t want to try non-production code yet, there’s a ‘hammer dedup-simulate’ command that will estimate the saving ratio.
This is great news – deduplication is so valuable it adds an extra zero onto the price of any storage device that can do it.
DragonFly has shipped with a uniprocessor kernel by default forever. Shipping with a SMP kernel may not work as well for all possible combinations. With some recent changes by Matthew Dillon, both types of kernel are present and can be picked from at boot time – with the LiveCD!
Venkatesh Srinivas has a large writeup describing just how the memory allocator in DragonFly changed from 2.6 to the upcoming 2.8 version. In all that text, you may notice the cheering statistic that it gave a 20% improvement in sysbench results.
Rumko came up with some changes for vkernel(7) that, among other things, made it possible to run them diskless; almost like booting a thin workstation.
OpenSSL on DragonFly can now dynamically load engines (cryptographic support modules) at runtime, thanks to Peter Avalos.
Matt Dillon and Venkatesh Srinivas conspired to fix another nmalloc issue, which should resolve any remaining problems people were having with Firefox, and possibly other applications as well. Due to an oversight of sorts, all locking operations on nmalloc’s depot were ineffective, as if there were no locking at all. Curiously, it worked remarkably well considering such a large race condition was present.
Here’s something: Pratyush Kshirsagar came along, saw the proportional RSS project idea, and did it. It’s nice to have a completed project just sort of fall out of the sky.
I’m linking to this commit message from Matthias Schmidt simply because it has the correct invocation for installing a vkernel, and I know this will come in handy, someday.
It looks like my prior article was incorrect: it was a different issue than MADT causing problems with booting x86_64. Scrambled memory report appears to be at the heart of the issue; in any case, it’s fixed now.
A bump in shared library version for libssl/libcrypto means that any programs dependent on it will require a rebuild – including any pkgsrc programs.
This only affects you if you are running 2.7, for now. It means that on upgrading from 2.6 to 2.8, any libssl-using programs will need to be updated. This may not be a big thing, since pkgsrc-2010Q3 will also be out and people will want to upgrade anyway.
Did you know Fred is the name for the DragonFly mascot? Well, you do now. He’s also back in the bootloader, thanks to Joe Talbott.
In an effort to support a new system with an AMD 880G chipset, Matthew Dillon has updated the AHCI driver. If you have SATA drives using AHCI, please test. (with any chipset, not just 880G.)
Two recent changes in the way virtual kernels are constructed should make a speed difference. The startup time is reduced (and more memory can be given to the vkernel), and the overall running speed should be quicker, too.
DragonFly’s version of pf (corresponding with OpenBSD’s 4.2 version) is now multiprocessor safe, to match the network stack. pf itself isn’t using multiple processors; it’s just able to work without causing problems in an otherwise MPSAFE environment, thanks again to Jan Lentfer. Note that there’s one minor caveat.