Date: Wed, 03 Jul 2002 12:57:50 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Julian Elischer <julian@elischer.org> Cc: freebsd-current@freebsd.org, Andrew Gallatin <gallatin@cs.duke.edu> Subject: Re: KSE signal problems still Message-ID: <XFMail.20020703125750.jhb@FreeBSD.org> In-Reply-To: <Pine.BSF.4.21.0207030927170.1443-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03-Jul-2002 Julian Elischer wrote: > > > On Wed, 3 Jul 2002, John Baldwin wrote: > >> >> The argument could be made that you shouldn't be checking in stuff >> until you know how it works, etc., or that you could commit in smaller >> pieces (say, get multiple threads per process for kernel processes >> working in the scheduler and just ignoring userland-only things like >> signals until you have the other working). > > You can't do those separatly unfortulatly.. Sure you could, just have kernel-only KSE processes at first and use some special kernel processes for testing. They would never return to userland but would be adequate to test that all the various run and sleep queues, etc. worked fine. > anyhow, it's not that I don't understand it, it's just that > it's complicated.. That part of my message was overly harsh. I'm sorry. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.20020703125750.jhb>