From owner-freebsd-hackers Thu Apr 22 15:24:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id BC7AD14D74 for ; Thu, 22 Apr 1999 15:24:19 -0700 (PDT) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id HAA77865; Fri, 23 Apr 1999 07:50:21 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199904222220.HAA77865@gizmo.internode.com.au> Subject: Re: flock + kernel threads bug To: eischen@vigrid.com (Daniel Eischen) Date: Fri, 23 Apr 1999 07:50:21 +0930 (CST) Cc: dick@tar.com, luoqi@watermarkgroup.com, hackers@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au In-Reply-To: <199904221957.PAA24764@pcnet1.pcnet.com> from "Daniel Eischen" at Apr 22, 99 03:57:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > > If the threads > > are kernel threads, how do you communicate to the kernel which thread > > you're acting on if the threads are "anonymous" in userland? > > You still have thread IDs in userland, but you now add: > _lwp_kill, _lwp_setschedparam, etc, > system calls to control the kernel threads. Or maybe one big > _lwp_control... If you make the BSD API the same as the SysVR4 API it'll make emulating it really easy :-) lwp_info lwp_sema_wait lwp_sema_post lwp_sema_trywait lwp_create lwp_exit lwp_suspend lwp_continue lwp_kill lwp_self lwp_getprivate lwp_setprivate lwp_wait lwp_mutex_unlock lwp_mutex_lock lwp_cond_wait lwp_cond_signal lwp_cond_broadcast lwp_sigredirect lwp_alarm - mark ---- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message