From owner-freebsd-arch Sat Nov 20 20:35:56 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id D7B6A15747 for ; Sat, 20 Nov 1999 20:35:42 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id FAA23123 for ; Sun, 21 Nov 1999 05:35:42 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id FAA12197 for freebsd-arch@freebsd.org; Sun, 21 Nov 1999 05:35:42 +0100 (MET) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 870FD15747 for ; Sat, 20 Nov 1999 20:35:32 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from vigrid.com (pm3-pt25.pcnet.net [206.105.29.99]) by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id XAA04007; Sat, 20 Nov 1999 23:35:29 -0500 (EST) Message-ID: <38377677.7AF35412@vigrid.com> Date: Sat, 20 Nov 1999 23:35:03 -0500 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Matthew Jacob , freebsd-arch@freebsd.org Subject: Re: Threads stuff References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > On Sat, 20 Nov 1999, Matthew Jacob wrote: > > > > Sure- that's kernel stuff, but it doesn't really work much in the area I > > would be interested, namely making interrupt and other kernel threads > > (e.g., for CAM device inventory management) for all drivers that could use > > them (an interrupt thread per interrupt entry point is not unreasonable), > > replacing all spl type locking with mutex_init (based on device interrupt > > levels) and mutex_enter/mutex_exit usages, perhaps replacing sleep/wakeup > > which is a per-process thingie with cv_wait/cv_signal.. you know, that > > kinda low level kernel I/O stuff- more nuts and bolts and less > > theoretical. When the discussion gets around to these things and policies > > about whether SMP safe and SMP-unsafe drivers can coexist, then I'll be > > more than happy to waste everyone's time with my opinions. > > But it's all inter-related.. The KSE allocator would be the same > KSE allocator that would be used to innitially allocate KSEs for > interrupt handling. (My secret agenda starts to show). My aim is to > get the BSDI "lazily evaluated threads" interrupt scheme. however the > threads they would be evaluating to would be the same KSEs that would > be allocated to the User thread scheme.. > > "A thread is a thread is a thread" > > Believe me my heart is in the "low level more nuts and bolts". I just see > a convergence of needs here. > > We certainly need someone to help with the KSEs and specifically the Mutexy > stuff. That should be quite applicable to both ends.. There's some good articles on locking too. Perhaps that should be another topic on -arch ;-) I agree with Matt and want to see mutex_enter, mutex_exit, cv_wait, cv_signal, etc, as opposed to sleep/wakeup. Count me in as wanting to help with "mutexy" stuff as well as threads. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message