Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming.threads > #159

Re: What it means to be first.

Show all headers | View raw

J de Boyne Pollard wrote:

>>       4. If the thread hadn't run on any of the selected processors
>>       before becoming a blocked thread, select the first processor
>>       that was found in the search.
>
> Unless there's some ordering defined for a set of processors,
> that's not a very meaningful constraint, since it lacks a concrete
> definition of "first" that can be relied upon. ("first" by processor
> number? "first" by processor interrupt arbitration priority? "first"
> in order of address in kernel space of some per-processor data
> structure? "first" in some linked list that was scanned? "first"
> in processor bootstrap order? All are conceivable implementation
> strategies/side-effects.) Is there such an ordering given in what you
> read?

I gave the URL for the document; you could have looked yourself :-)

Anyway, I have searched it for all occurrences of "processor" and
didn't find anything relevant.

-- 
Geoff Clare <netnews@gclare.org.uk>

Back to comp.programming.threads | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: What it means to be first. J de Boyne Pollard <j.deboynepollard@tesco.net> - 2011-05-17 02:21 -0700
  Re: What it means to be first. Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2011-05-17 13:22 +0100

csiph-web