Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jun 2003 20:49:45 -0400 (EDT)
From:      Daniel Eischen <eischen@vigrid.com>
To:        Julian Elischer <julian@elischer.org>
Cc:        freebsd-threads@freebsd.org
Subject:   Re: The first kse_create call
Message-ID:  <Pine.GSO.4.10.10306172048010.13425-100000@pcnet5.pcnet.com>
In-Reply-To: <Pine.BSF.4.21.0306171527190.31025-100000@InterJet.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Jun 2003, Julian Elischer wrote:
> 
> On Tue, 17 Jun 2003, Daniel Eischen wrote:
> > This is the correct behavior.  The first kse_create() does not
> > generate an immediate upcall.  It only flags the current context
> > as being a KSE.  An upcall in this initial KSE will take place
> > under the same conditions as other KSEs (KSE mailbox has a thread
> > mailbox pointer and thread blocks, quantum expires, etc).
> > Subsequent kse_create() calls will generate upcalls immediately
> > (well, at the mercy of the kernel scheduler).
> 
> Wellll, the kse_create() will not upcall, but the new kse that is
> created will upcall.

Right, that's what I meant.

> The kse_create() call will just return to the original thread.

Yup.

-- 
Dan Eischen



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10306172048010.13425-100000>