| From | Sent On | Attachments |
|---|---|---|
| Julian Elischer | Oct 31, 1999 11:57 am | |
| Julian Elischer | Oct 31, 1999 1:15 pm | |
| Kris Kennaway | Oct 31, 1999 2:00 pm | |
| Amancio Hasty | Oct 31, 1999 2:11 pm | |
| Julian Elischer | Oct 31, 1999 2:38 pm | |
| Kris Kennaway | Oct 31, 1999 3:09 pm | |
| Nate Williams | Oct 31, 1999 3:40 pm | |
| Daniel Eischen | Oct 31, 1999 3:43 pm | |
| Daniel Eischen | Oct 31, 1999 3:53 pm | |
| Daniel C. Sobral | Oct 31, 1999 4:48 pm | |
| Nate Williams | Oct 31, 1999 4:54 pm | |
| Julian Elischer | Oct 31, 1999 5:08 pm | |
| Peter Jeremy | Oct 31, 1999 5:15 pm | |
| Nate Williams | Oct 31, 1999 5:15 pm | |
| Julian Elischer | Oct 31, 1999 5:41 pm | |
| Julian Elischer | Oct 31, 1999 5:49 pm | |
| Julian Elischer | Oct 31, 1999 6:16 pm | |
| Nate Williams | Oct 31, 1999 6:19 pm | |
| Nate Williams | Oct 31, 1999 6:20 pm | |
| Amancio Hasty | Oct 31, 1999 6:31 pm | |
| Julian Elischer | Oct 31, 1999 6:44 pm | |
| Daniel Eischen | Oct 31, 1999 7:01 pm | |
| Nate Williams | Oct 31, 1999 7:02 pm | |
| Daniel Eischen | Oct 31, 1999 7:14 pm | |
| Daniel Eischen | Oct 31, 1999 7:16 pm | |
| Daniel Eischen | Oct 31, 1999 7:46 pm | |
| Nate Williams | Oct 31, 1999 8:12 pm | |
| Daniel Eischen | Oct 31, 1999 8:53 pm | |
| Marcel Moolenaar | Nov 1, 1999 1:56 am | |
| Randell Jesup | Nov 1, 1999 3:12 am | |
| Nate Williams | Nov 1, 1999 7:28 am | |
| Justin T. Gibbs | Nov 1, 1999 9:05 am | |
| Nate Williams | Nov 1, 1999 11:07 am | |
| Justin T. Gibbs | Nov 1, 1999 11:14 am | |
| Peter Dufault | Nov 1, 1999 11:36 am | |
| Daniel Eischen | Nov 1, 1999 11:54 am | |
| Nate Williams | Nov 1, 1999 12:01 pm | |
| Nate Williams | Nov 1, 1999 12:02 pm | |
| Nate Williams | Nov 1, 1999 12:16 pm | |
| Daniel Eischen | Nov 1, 1999 12:36 pm | |
| Daniel Eischen | Nov 1, 1999 12:52 pm | |
| Nate Williams | Nov 1, 1999 12:59 pm | |
| Peter Dufault | Nov 1, 1999 1:04 pm | |
| Julian Elischer | Nov 1, 1999 1:18 pm | |
| Peter Dufault | Nov 1, 1999 1:22 pm | |
| Jacques Vidrine | Nov 1, 1999 2:43 pm |
| Subject: | Re: Threads models and FreeBSD. | |
|---|---|---|
| From: | Peter Jeremy (jere...@gsmx07.alcatel.com.au) | |
| Date: | Oct 31, 1999 5:15:19 pm | |
| List: | org.freebsd.freebsd-arch | |
[This should have gone to the list, not just Julian]
On 1999-Nov-01 08:15:23 +1100, Julian Elischer wrote:
So what are the definitions that a thread enabled environment should possess?
One good starting point would be some agreement on terminology since /usr/include/sys/proc.h states: * This structure contains the information needed to manage a thread of * control, known in UN*X as a process;
For the purposes of this discussion, I suggest that `process' refers to 1 or more threads sharing a common address space. This is distinct from the usage within 4.4BSD - particularly rfork(2).
2/ Ability to simultaneously schedule two threads over separate Processors.
^^^ N ^ N
6/ (contentious) multiple theads should be bound to within the resource limits of the single process.
Whilst some of this is `implementation' rather than `requirements', a good place to start is to work through each field in struct proc and decide whether that information relates to the process as a whole, or a single thread. (This will need to be done at some stage, and is a good trigger for deciding what differentiates a thread from a process).
Peter
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message





