From owner-freebsd-arch Sun Aug 26 13:15: 7 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 3806437B40B for ; Sun, 26 Aug 2001 13:15:03 -0700 (PDT) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id NAA46406; Sun, 26 Aug 2001 13:10:07 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f7QKA6f28508; Sun, 26 Aug 2001 13:10:06 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200108262010.f7QKA6f28508@arch20m.dellroad.org> Subject: Re: changes to BSD APIs for THREADS support In-Reply-To: <3B885ED0.9DFCA5B5@elischer.org> "from Julian Elischer at Aug 25, 2001 07:28:32 pm" To: Julian Elischer Date: Sun, 26 Aug 2001 13:10:06 -0700 (PDT) Cc: arch@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer writes: > 5/ It is possible that we may need a call by which the user thread > scheduler can 'cancel' the syscall that a particular kernel thread > is currently operating on. (particularly if it is waiting). I think this is going to be required. The UTS needs to have the ability to cancel a thread at any time. If the thread is in userland then it can just do it; otherwise it needs a way to wake up the thread in the kernel. The thread's syscall should then return immediately with EINTR or somesuch; alternately, the thread can just never return. Mabye both options would be good to have. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message