>>>>> "AB" == Arthur Bergman <[EMAIL PROTECTED]> writes:
AB> In an effort to rest my braine from a coredumping perl5 I started
AB> to think a bit on threading under parrot? While it has been
AB> decided that perl should be using ithread like threading, I guess
AB> that is irelevant at the parrot level. Are you going to have one
AB> "virtual cpu" per thread with it's own set of registers or are you
AB> going to context switch the virtual cpu?
it is not irrelevent IMO. since each thread will have a private parrot
interpreter, then parrot must minimize any globals so it can be almost
all stack based. this means the parrot control structure must be
malloc'd and only one pointer to it must be in some sort of global space
(for thread management). this structure will manage the PC, the stacks,
thread global vars, memory management (with or without gc?), etc.
AB> If it was one virtual cpu per thread then one would just create a
AB> new virtual cpu and feed it the bytecode stream?
that is the idea as i have understood it.
AB> Is there anything I could help with regarding this?
i think we need to design the (async) i/o and event subsystems either
before or in parallel to the thread subsystem. they will all be coupled
in various ways and it is better to do all the design first so you don't
have awkward interfaces later.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture and Stem Development ------ http://www.stemsystems.com
Search or Offer Perl Jobs -------------------------- http://jobs.perl.org
