Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 Oct 1999 19:25:32 -0700
From:      Nate Williams <nate@mt.sri.com>
To:        Julian Elischer <julian@whistle.com>
Cc:        freebsd-arch@freebsd.org
Subject:   Re: Threads goals  version II
Message-ID:  <199911010225.TAA14010@mt.sri.com>
In-Reply-To: <Pine.BSF.4.05.9910311817030.8816-100000@home.elischer.org>
References:  <Pine.BSF.4.05.9910311817030.8816-100000@home.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> ---Possible  system design goals of system threads support --
> --- Note just becasue something is in this list doesn't mean that
> it will be done, just that it's going o be carried forward to
> further discussion.
> --------------------------------------------------------------
> 
> 1/ Multiple independent 'threads of control' within a single process
>   at user level. The most basic quality of threads.
> 
> 2/ Ability to simultaneously schedule M threads over N Processors.
>  2A/ ability to tune and control the above..
>  
> 3/ One blocking thread cannot block another thread.
>         Blocking of one thread does not imply that other threads be
> blocked.

How about instead of 'cannot' we use the word 'does not necessarily'
block another thread, and then append 'unless it does using programatic
means'.

Cannot implies some sort of bad thing.

> 4/ All threads see the same address space (exactly).

I like this.

> 5/ All threads share the same file resources.

How about 'process' resources instead?  It's more than files that they
share...

> 10/ Quick access to curthread and thread specific data.  We shouldn't
>        have to enter the kernel to get this.  This should also be true
>        for threads spread across multiple [lightweight] processes.

The last sentence is redundant, since threads are by definition
lightweight processes. :)

> 11/ Ability for the threads library to cancel/terminate a thread
>        blocked in the kernel.

See previous email.



Nate




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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911010225.TAA14010>