This week Matt Dillon is doing:
- lwkt_token and IPI code optimization
- GCC 3.x (just for support of the next item)
- 64 bit AMD64 support
… and networking code with Jeff Hsu.
For those of you late to the party and wondering why his work schedule is spotlighted, Matt Dillon is the originator of the DragonFly project, and is doing much heavy lifting.
Jeroen Ruigrok and Matt Dillon wrote up an article for BSDNews.org about DragonFly.
Not directly about DragonFly, but chances are good you are using it. Release 4.4 of XFree86 is due by the end of the month, and you can look at the changelog.
Matt Dillon’s added boot code from FreeBSD 5 – this allows AMD64 and ELF64 support. He also pushed in new linker code and some (not yet enabled) support for UFS2.
Use installkernel and installworld as part of your build process, and you should be fine with these changes. However, you will manually have to copy
There’s been a lot of new code lately – that’s good!
Variant symlinks are possible now, though you currently have to set the sysctl vfs.varsym_enable. ‘varsym’ can be used to mess with them at any time, however.
Joshua Coombs has updated his writeup of a new routing model, based on feedback.
Matt Dillon’s reorganizing some of the header files; if you build a new kernel anytime soon, make sure you build from scratch using ‘config -r’, as some of the old header files have now vanished.
Congratulations are due to committer Jeroen Ruigrok, who is apparently getting hitched.
Changes to systat by Kenneth Culver gives it the ability to show each network interface and its throughput.
Jeffrey Hsu and Matt Dillon’s network changes are being committed – the first third is in, according to a commit by Matt.
Matt describes the plan thusly:
“Basically the goal of this work is to isolate and serialize PCBs in specific threads in order to (A) not have to lock them and (B) improve cache locality for ISR processing loops as well as for data. Isolating a network PCB means dealing with the points where the PCB talks to other parts of the system. There are three points where this happens:
- incoming packets go through preprocessing (e.g. IP) before
being routed to the target protocol & PCB (e.g. TCP and UDP).
- user syscalls operate on PCBs
- timers and such initiate work related to particular PCBs”
I wish I knew what a PCB was.
Matt Dillon posted an interesting bit about what’s needed/planned for non-emulated use of the AMD64:
Continue reading “Not long until Long”
This site was mentioned in the BSD News section of the November DaemonNews ezine. Neat!
Plus, I’ve reached 100 posts! This is actually the 102nd, if I’m counting right, minus early test posts.
Aaaaand I broke the mailarchive.
Matt Dillon’s putting in some material from FreeBSD-5, so if PNPBIOS is defined, you may not produce a working kernel during the next few days.
update: PNPBIOS should not be enabled if you have a AMD64 machine, and the K8V motherboard, as that appears to be broken.
Jeroen Ruigrok is setting up Bugzilla for tracking bugs/requests for DragonFly. As part of the process, there’s some 6,000 (!) items brought over from FreeBSD-4. No link yet…
The 3c940 ethernet driver (found on ASUS K8V motherboards) is now supported. It’s the ‘sk’ device. Matt Dillon’s AMD64 machine apparently arrived.
I was pointed at the gmane.org site to find old dragonfly.kernel postings. I moved in what was there, and so the local kernel archive has several months of history added in, now. Docs doesn’t seem to be working yet…
David Rhodus has been commiting a whole bunch of fixes from FreeBSD today. You can tell just by looking at the mailing list archive for commits@, freshly set up, and updated hourly along with the other archives.
Anyone have old list traffic sitting around, perhaps in mbox format? I’d like to backfill.
send-pr, the strange commandline utility for making a bug report, now goes to the bugs mailing list.
Byron Schlemmer put up Matt Dillon’s slides from his Berkley talk as HTML pages.