NYCBUG, the NY BSD user’s group, has an RSS feed for their speaker events, found via Dru Lavigne’s always useful BSD Events twitter. The next event at the start of October is a talk about SMPng in FreeBSD. Given that it was the project that in part led to the creation of DragonFly, I’d like to hear about it. (and even better, have someone more qualified than I compare and contrast that approach with what’s in DragonFly.)
If you do, they don’t get cleaned up during the normal ‘hammer cleanup’ nightly routine. Chris Turner has added a way to manually specify them as a cleanup target.
I’m pretty sure in this case ‘offline’ means ‘nothing streaming to it from a master disk’. I think.
Matthew Dillon has created an experiment: shared page table mappings. It’s controlled by a sysctl, since it’s still experimental. The real-world effect is reducing the number of memory faults as a process uses up memory, and decreasing the overall memory usage. The obvious benchmark is Postgres speed; this makes the initial expansion of memory usage much less of an drag on speed due to a high memory fault rate.
If all this mention of faulting sounds like a problem, remember memory faults on BSD are normal; that’s how programs indicate they need more memory space by causing a fault. This is in contrast to Linux, where memory is allocated a different way. Or at least, that’s my understanding. (If you know better, please comment.)
If you are using an Intel 10G Ethernet card with a 82598GB chipset, you’re using ixgbe(4). You may want to set the net.inet.tcp.sosend_agglim sysctl to a value over 12 in certain circumstances, as described by Francois Tigeot.
These are small, but they make life easier: Hammer now has a scoreboard file, for viewing of mirror-streams running in the background. There’s also a ssh-remote directive, so you can use ssh without enabling an interactive shell, and a HAMMER_RSH environment variable so different remote shells can be used. These are all for Hammer 1.
If you ever wanted to read an extensive discussion about the scheduler, today’s your day. Mihai Carabas, who posted the details of a long discussion he had with Matthew Dillon about how the scheduler works. You may recall Mihai’s name from the very successful GSoC scheduler project that recently finished.
(look, a link to the new Mailman archive!)
All the mailing lists at @dragonflybsd.org have been converted over to Mailman. The old archives are still functioning, and will continue to update until I can find enough old material to retroactively complete the Mailman archives.
If you’re on any of the dragonflybsd.org mailing lists, I’m converting them over from bestserv to Mailman. I’ve done bugs@, commits@, hammer@, and test@ so far, and I’ll move the old archives over to the same format as soon as I find an actual mbox file with the old messages in it. The remaining lists should be tomorrow.
(If you got a note tonight from a list you were sure you were unsubscribed from, that was my fault; sorry! I didn’t understand the format of the bestserv user lists.)
DragonFly user varialus has created a page on the DragonFly website (it’s a wiki, after all) with all the notes taken from trying installation, etc. There’s far more notes than I expected there, so it’s worth a read.
Much of this new document has been around in other forms for a while, but now, there’s a brief guide on porting drivers to DragonFly in the source tree.
Because here’s some recommendations on good models, and here’s a way to check SSD health. Seriously, they’re great.
I’ve uploaded DragonFly 3.0.3 disk images, both ISO and IMG. They should start appearing on a mirror site near you in the next 24 hours. This took a while after the tagging, I know, but I wanted to make sure every one of them booted. I didn’t on a previous release, and regretted it.
If you have a LSI RAID card, meaning you are using the mfi(4) driver, Sascha Wildner has added /proc/devices to linprocfs, so that LSI’s MegaCLI configuration utility will run.
Sascha Wildner has pushed smart battery support, based on a patch from Dmitry Komissaroff and FreeBSD. He asks people to try it out. It apparently provides for more accurate battery charge level readings?
Francois Tigeot benchmarked several different operating systems using Postgres 9.2b3, including DragonFly, and published the results. I have a local copy of the PDF since the attachment didn’t really survive the archiving. Follow the thread for discussion. The Linux results look abnormally high, so it is possible that something different is happening on that platform…
Do you happen to have the saved messages for one or more @dragonflybsd.org mailing lists sitting around? Hopefully in mbox format? I’m working on getting Mailman installed to replace bestserv, and being able to bring in the old messages would be nice.
I’m working on building new images, but: DragonFly 3.0.3 has been tagged. If you’re running 3.0, you can update and get some of the recent bug fixes.
I noticed that this recent commit from Sepherosa Ziehau is a bug fix for jme(4). The commit thanks a JMicron employee for help. It’s always appreciated when a vendor is helpful to an open-source project for hardware support. It’s also something you should consider the next time you are shopping for computer parts.
Antonio Huete has updated dhclient(8) to match the OpenBSD version from whence it comes. I think all (most?) the BSDs use the OpenBSD dhcp client as a base now. The only user-facing change I see in a quick reading of the changes is a new ‘egress’ command line option.
John Marino has been on a tear fixing pkgsrc packages, and he posted a list of what he considers the most necessary packages to get working on DragonFly. Several people have already stepped up and fixed them if you follow the thread. If one of these packages is something you use, it’s worth looking at.