Date: Tue, 30 Apr 2002 09:49:53 -0700 (PDT) From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Cc: jeff@freebsd.org Subject: src/sys/kern/kern_malloc.c (rev. 1.104) seems OK so far.... Message-ID: <200204301649.g3UGnrbC078367@bunrab.catwhisker.org>
next in thread | raw e-mail | index | archive | help
I don't normally post when things appear to work, but since I had mentioned that I had seen some problems with rev. 1.99 of src/sys/kern/kern_malloc.c, I thought it only fair to point out that I noted the small flurry of recent commits to that file, re-synced it with the CVS repository, built -CURRENT with it, and survived the reboot and initial testing OK -- both on my SMP build machine and my uniprocessor laptop. Here's unmae -a from the latter: g1-9(5.0-C)[1] uname -a FreeBSD g1-9.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #35: Tue Apr 30 09:16:08 PDT 2002 root@g1-9.catwhisker.org:/common/S3/obj/usr/src/sys/LAPTOP_30W i386 g1-9(5.0-C)[2] I'm not going to be so silly as to claim it (or anything else!) is perfect; this is a work by humans, after all. But it's a lot better than it was. I'll give it more of a stress-test tomorrow, when I try doing tomorrow's -CURRENT buildworld (& friends) while running today's. Cheers, david -- David H. Wolfskill david@catwhisker.org Microsoft products -- for those times when reliability just doesn't matter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204301649.g3UGnrbC078367>