From owner-freebsd-arch Fri Nov 12 0:22:34 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 925E814CEB for ; Fri, 12 Nov 1999 00:22:30 -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 JAA11730 for ; Fri, 12 Nov 1999 09:22:29 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id JAA16540 for freebsd-arch@freebsd.org; Fri, 12 Nov 1999 09:22:29 +0100 (MET) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id E11D614C0B for ; Fri, 12 Nov 1999 00:21:26 -0800 (PST) (envelope-from michael.schuster@germany.sun.com) Received: from emuc05-home.Germany.Sun.COM ([129.157.51.10]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA07443; Fri, 12 Nov 1999 00:21:20 -0800 (PST) Received: from germany.sun.com (hacker [129.157.167.97]) by emuc05-home.Germany.Sun.COM (8.8.8+Sun/8.8.8/ENSMAIL,v1.7) with ESMTP id JAA08497; Fri, 12 Nov 1999 09:21:07 +0100 (MET) Message-ID: <382BCDF7.8689BA4B@germany.sun.com> Date: Fri, 12 Nov 1999 09:21:11 +0100 From: Michael Schuster - TSC SunOS Germany Organization: Sun Microsystems, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Eischen Cc: "freebsd-arch@FreeBSD.ORG" Subject: Re: Threads goals and implementation References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > On Thu, 11 Nov 1999, Michael Schuster - TSC SunOS Germany wrote: [...] > > > 9/ There exists a set of primatives that allow threads to influence the > > > in-process scheduling between themselves. > > > 9A/ e.g. 'per thread' Thread scheduling classes. > > > > scheduling class is an attribute of a thread, therefore a resource -> > > ergo contradiction to 5/ & 6/ > > This doesn't have to imply scheduling across all threads in the system. > It does state "in-process" scheduling, so I don't think that 9A is > meant to include system scheduling classes. I actually didn't mean to say so, so yes, I agree with you here (am I contradicting myself? I don't really think so :-) > > my suggestion: > > > > 5/ All threads in a process share the same resources by default with > > the following possible exceptions > > 5a/ the (limits for) the following resources can be set on a > > per-thread basis: priority, quantum, scheduling class.. (your favourite > > here) > > 5b/ thread-specific data such as curthread, thread stack, etc. > > > > and do away with 6/, 9/, 10/ and 13/ > > Makes sense to me, though I think that "quick access to TSD and current > thread" is a goal. I meant to say that, I must have lost it somewhere. :-) > Dan Eischen > eischen@vigrid.com cheerio Michael -- Michael Schuster / Michael.Schuster@germany.sun.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message