Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Dec 1999 08:08:20 -0500
From:      "Daniel M. Eischen" <eischen@vigrid.com>
To:        Julian Elischer <julian@whistle.com>, arch@freebsd.org
Subject:   Re: Recent face to face threads talks.
Message-ID:  <38539E44.537A57E@vigrid.com>
References:  <Pine.BSF.4.10.9912112354520.26823-100000@current1.whistle.com> <38539C2B.9632089A@vigrid.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I should caffeinate before reading Email!

"Daniel M. Eischen" wrote:
> Yes, we can pass the trapframe/context of a preempted or unblocked thread
> out to the upcall handler and not have to use a different call-gate.
> One advantage of another call-gate could be faster access to the
> unblocked thread.  In order for the UTS to locate an unblocked thread
> from the information provided in the upcall, the UTS has to walk the
> unblocked thread list looking for the KSE ID.  If you use another
  ^^^^^^^^^ blocked
> syscall-gate and provide the address of an IOCB, the address of the
> IOCB can be given to the blocked upcall handler.  The UTS can then
> place the pointer to the thread struct in the IOCB.  When the thread
> unblocks, the address of the IOCB is provided to the upcall handler
> and the UTS can just dereference it to find the thread struct.
> 
> Dan Eischen
> eischen@vigrid.com




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?38539E44.537A57E>