From owner-freebsd-threads@FreeBSD.ORG Tue Jun 17 17:49:51 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5434F37B401 for ; Tue, 17 Jun 2003 17:49:51 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B22F43FBF for ; Tue, 17 Jun 2003 17:49:50 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h5I0njXh015437; Tue, 17 Jun 2003 20:49:45 -0400 (EDT) Date: Tue, 17 Jun 2003 20:49:45 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Julian Elischer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Sergey Kosyakov cc: freebsd-threads@freebsd.org Subject: Re: The first kse_create call X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 00:49:51 -0000 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