atom feed76 messages in org.freebsd.freebsd-archRe: Threads
FromSent OnAttachments
Daniel M. EischenNov 20, 1999 8:12 pm 
Julian ElischerNov 20, 1999 8:30 pm 
Julian ElischerNov 20, 1999 8:37 pm 
Daniel M. EischenNov 20, 1999 9:02 pm 
Nate WilliamsNov 20, 1999 9:14 pm 
Daniel M. EischenNov 20, 1999 9:21 pm 
Julian ElischerNov 20, 1999 9:25 pm 
Nate WilliamsNov 20, 1999 9:27 pm 
Daniel M. EischenNov 20, 1999 9:40 pm 
Julian ElischerNov 20, 1999 10:58 pm 
Daniel M. EischenNov 21, 1999 5:40 am 
Chuck RobeyNov 22, 1999 4:30 pm 
Julian ElischerNov 22, 1999 7:57 pm 
Chuck RobeyNov 22, 1999 8:11 pm 
Julian ElischerNov 22, 1999 8:38 pm 
Chuck RobeyNov 22, 1999 9:40 pm 
Daniel EischenNov 23, 1999 4:19 am 
Jason EvansNov 23, 1999 11:30 am 
Daniel M. EischenNov 23, 1999 1:22 pm 
Chuck RobeyNov 23, 1999 9:06 pm 
Daniel EischenNov 23, 1999 9:49 pm 
Julian ElischerNov 23, 1999 10:47 pm 
Julian ElischerNov 23, 1999 11:33 pm 
Julian ElischerNov 23, 1999 11:46 pm 
Julian ElischerNov 24, 1999 2:03 am 
Daniel C. SobralNov 24, 1999 3:19 am 
Daniel C. SobralNov 24, 1999 3:51 am 
Daniel M. EischenNov 24, 1999 6:03 am 
Richard Seaman, Jr.Nov 24, 1999 6:33 am 
Matthew DillonNov 24, 1999 10:35 am 
Daniel EischenNov 24, 1999 11:02 am 
Matthew DillonNov 24, 1999 11:05 am 
Anthony KimballNov 24, 1999 11:25 am 
Daniel EischenNov 24, 1999 11:28 am 
Matthew DillonNov 24, 1999 11:41 am 
Matthew DillonNov 24, 1999 11:47 am 
Julian ElischerNov 24, 1999 11:54 am 
Louis A. MamakosNov 24, 1999 11:57 am 
Matthew DillonNov 24, 1999 12:00 pm 
Julian ElischerNov 24, 1999 12:20 pm 
Anthony KimballNov 24, 1999 12:47 pm 
Doug RabsonNov 24, 1999 2:05 pm 
Jason EvansNov 24, 1999 2:16 pm 
Julian ElischerNov 24, 1999 2:28 pm 
Julian ElischerNov 24, 1999 2:40 pm 
Richard Seaman, Jr.Nov 24, 1999 3:39 pm 
Jason EvansNov 24, 1999 9:24 pm 
Jason EvansNov 24, 1999 10:03 pm 
Julian ElischerNov 25, 1999 1:08 am 
Julian ElischerNov 25, 1999 1:33 am 
Daniel M. EischenNov 25, 1999 3:08 am 
Doug RabsonNov 26, 1999 3:01 am 
Jordan K. HubbardNov 26, 1999 10:33 am 
Doug RabsonNov 26, 1999 12:15 pm 
Matthew DillonNov 27, 1999 7:38 pm 
Arun SharmaNov 27, 1999 8:57 pm 
Matthew DillonNov 28, 1999 8:41 am 
Arun SharmaNov 28, 1999 10:25 am 
Matthew DillonNov 28, 1999 5:06 pm 
Nate WilliamsNov 29, 1999 8:10 am 
Matthew DillonNov 29, 1999 8:21 am 
Nate WilliamsNov 29, 1999 8:29 am 
Matthew DillonNov 29, 1999 9:05 am 
Matthew DillonNov 29, 1999 9:19 am 
Daniel M. EischenNov 29, 1999 9:28 am 
Nate WilliamsNov 29, 1999 10:29 am 
Julian ElischerNov 29, 1999 11:23 am 
Nate WilliamsNov 29, 1999 1:39 pm 
Chuck RobeyNov 29, 1999 6:06 pm 
Daniel M. EischenNov 29, 1999 7:46 pm 
Chuck RobeyNov 29, 1999 9:01 pm 
Julian ElischerNov 29, 1999 9:34 pm 
Chuck RobeyNov 29, 1999 10:09 pm 
Daniel M. EischenNov 30, 1999 4:02 am 
Jason EvansNov 30, 1999 2:25 pm 
Julian ElischerNov 30, 1999 2:42 pm 
Subject:Re: Threads
From:Chuck Robey (chu@picnic.mat.net)
Date:Nov 23, 1999 9:06:32 pm
List:org.freebsd.freebsd-arch

On Tue, 23 Nov 1999, Daniel Eischen wrote:

I'm wondering if there might possibly be some way to preserve some level of simplicity by keeping ksid'd like we keep pid's now, so that things that juggle a 32 bit entity keep on doing that, although perhaps under another name.

I think you're basically right in keeping things simple. I think that a non-MT process should be equivalent to a MT process. The non-MT process has only one co-operating process (itself) and one KSE. Whenever the non-MT process blocks in the kernel, there are no more available KSEs, so another process is scheduled.

OK, then let me ask another question: are we at all concerned about maybe following an already established thread API, or are we going to create our own? Things like user threads probably could work as then are now (albeit perhaps with only minor changes in performance) and stuff with runtimes like Java wouldn't care, but big programs like XFree86 and Netscape, and specially made daemons trying to do things like mass factoring, that are going to really want to manipulate real concurrency levels, they're going to have to be aware of our real underlying API, so making a unique one will complicate a lot of lives.

Dan Eischen eisc@vigrid.com

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message