From owner-freebsd-java Sun Aug 26 17:10:31 2001 Delivered-To: freebsd-java@freebsd.org Received: from gnuppy.monkey.org (cx739861-a.dt1.sdca.home.com [24.5.164.61]) by hub.freebsd.org (Postfix) with ESMTP id 98BCE37B407 for ; Sun, 26 Aug 2001 17:10:28 -0700 (PDT) (envelope-from billh@gnuppy.monkey.org) Received: from billh by gnuppy.monkey.org with local (Exim 3.32 #1 (Debian)) id 15b9yq-0001zT-00; Sun, 26 Aug 2001 17:10:16 -0700 Date: Sun, 26 Aug 2001 17:10:10 -0700 To: Fuyuhiko Maruyama Cc: Arun Sharma , java@freebsd.org Subject: Re: JVM and native threads Message-ID: <20010826171010.A6742@gnuppy> References: <20010824233304.A32099@sharmas.dhs.org> <55vgjcqv87.wl@tripper.private> <20010825095746.A1015@sharmas.dhs.org> <55heuv0xtl.wl@tripper.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55heuv0xtl.wl@tripper.private> User-Agent: Mutt/1.3.20i From: Bill Huey Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Aug 26, 2001 at 10:12:38PM +0900, Fuyuhiko Maruyama wrote: > Yes, I also think we need to define some _np calls. To do so, we need > to consider what APIs are really needed, defined APIs are sufficient > and general enough. > > We must spend more time to discuss about this issue. The primary *_np stuff we need has to do with thread resume & suspension. It's used sparingly in a couple of places with varying levels of functional importance like the GC and during thread creation time (new threads are suspended only to be woken up by the spawning function after the stack is attach to the VM), etc... I'm struggling with OpenMotif issues right now and I'm kind of wondering why the current OpenMotif port is a release version behind what's being offered at their site ? bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message