From owner-freebsd-current Thu Oct 29 08:25:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12492 for freebsd-current-outgoing; Thu, 29 Oct 1998 08:25:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12486 for ; Thu, 29 Oct 1998 08:25:07 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.8.7) with SMTP id KAA14241; Thu, 29 Oct 1998 10:25:02 -0600 (CST) Message-Id: <199810291625.KAA14241@ns.tar.com> From: "Richard Seaman, Jr." To: "current@FreeBSD.ORG" , "eischen@vigrid.com" , "info@highwind.com" Date: Thu, 29 Oct 98 10:25:02 -0500 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Thread Scheduler bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998 11:10:06 -0500 (EST), Daniel Eischen wrote: >Yeah, I just figured this out (should pay closer attention to >the man pages). Seems like the profiling timer would be closer >to what we'd want (not to say the threads library should use >the profiling timer). A quick hack to replace occurrences of >SIGVTALRM with SIGPROF in the threads library seems to make >the test program work more correctly. > >Perhaps SIGALRM should be used instead of SIGVTALRM? Of course, it we had kernel threads, the pthreads code would be a *lot* simpler and maybe less prone to bugs, the kernel would do the preemption for us, and context switches would be much faster than the current user thread implementation. :) I've been poking around in the code, and I'd guess that a uniprocessor kernel threads implementation wouldn't involve all that much work. However, I understand there's are fair amount of kernel work that needs to be done for SMP kernel threads. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message