From owner-freebsd-arch Wed Dec 1 21: 7:35 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 3ED2814D63 for ; Wed, 1 Dec 1999 21:07:31 -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 GAA07142 for ; Thu, 2 Dec 1999 06:07:26 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id GAA80659 for freebsd-arch@freebsd.org; Thu, 2 Dec 1999 06:07:25 +0100 (MET) Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E255914D49 for ; Wed, 1 Dec 1999 21:07:07 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA57954 for ; Thu, 2 Dec 1999 00:04:58 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Thu, 2 Dec 1999 00:04:58 -0500 (EST) From: Chuck Robey To: arch@freebsd.org Subject: Threads - kernel call costs In-Reply-To: <19991201085633.Z29767@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm reading more about threading strategies, and I realize a real comparison is going to depend very heavily on the real costs involved with getting the kernel to perform some basic tasks. From some things that Matt Dillon has said a little while back, I get the idea that there might even be some corners that might be cut, under the right conditions. I'm wondering at the costs involved in getting the kernel to do an upcall to a UTS. Also, what would the cost be, to get the kernel to do a context switch on a thread, given that there would be no switch in the memory area. I would also like to know the costs involved in installing signal handler masks, and vectors of signal handlers. I haven't seen enough on these topics, but one really can't come to any true conclusion on threading strategies without it. I'm not personally familiar with this, so I'm hoping others are. If you have more than one answer (say, if you give a range of 5 to 100 microseconds for something) then include reasons that would tend to make it be in the longer or shorter end of the range. Thanks. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message