From owner-freebsd-hackers Thu Apr 22 16:57:34 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 5A2B91512D for ; Thu, 22 Apr 1999 16:57:22 -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 JAA78068; Fri, 23 Apr 1999 09:23:38 +0930 (CST) (envelope-from newton) From: Mark Newton Message-Id: <199904222353.JAA78068@gizmo.internode.com.au> Subject: Re: flock + kernel threads bug To: eischen@vigrid.com (Daniel Eischen) Date: Fri, 23 Apr 1999 09:23:38 +0930 (CST) Cc: eischen@vigrid.com, newton@internode.com.au, dick@tar.com, hackers@FreeBSD.ORG, luoqi@watermarkgroup.com, peter.jeremy@auss2.alcatel.com.au In-Reply-To: <199904222326.TAA21462@pcnet1.pcnet.com> from "Daniel Eischen" at Apr 22, 99 07:26:54 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: > Mark Newton wrote: > > > 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 :-) [ list of SysVR4 syscalls deleted ] > Seems like a good idea to me. But are these all system calls, or are some > library routines? Having lwp_self be a system call doesn't seem optimal. They're all syscalls (or, at least, they all have syscall numbers reserved for them). - 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