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.
Eirik Nygaard has also cleaned out all the __P() in usr.bin and usr.sbin, and incidentally gained a commit bit. Congrabulations.
In a thread about booting media, Matt Dillon noted he was going to:
- Look at Jeff Hsu’s TCP thread code
- implement variant symlinks
- start VFS messaging and environments
VFS will make a number of other things – especially a new port system – possible.
James Frazer found, and David Rhodus corroborated, that NTFS support tain’t working.
till noted in a comment here that www.dragonflybsd.de is live, and is using the RDF feed from this site.
Eirik Nygaard submitted a patch that removes over 700 instances of __P() from src/sbin/. It’s been committed.
Matt Dillon explained what he wants the port-creation experience to be for a port maintainer, using VFS, quoted below:
Continue reading “VFS and ports for maintainers”
Hiten Pandya mentioned that Robert Watson has set up the FXR website (FreeBSD/Linux Cross Reference) for BSD code. It’s a personal domain, so please don’t tax it at present.
Greg Lehey put up a paper and slides from his Singapore presentation, describing the FreeBSD-5 SMPng work, both in terms of events and code. It’s an interesting read, since this is the path avoided in DragonFly. (Greg Lehey has a 2001 USENIX paper on SMPng, too, which mentions much of the same content.)
Jeroen Ruigrok has fixed
On the freebsd-hackers mailing list, a slight flamewar erupted over discussion of checkpointing code from DragonFly. Amidst the dumbness that normally ensues in a flamewar, there’s some interesting descriptions on what work has been done/will be done on DragonFly. Check out the archive, mostly in the “FreeBSD mail list etiquette” thread. Matt Dillon’s posts here, here, and here are all info-packed.