Date: Sun, 26 Aug 2001 13:10:06 -0700 (PDT) From: Archie Cobbs <archie@dellroad.org> To: Julian Elischer <julian@elischer.org> Cc: arch@freebsd.org Subject: Re: changes to BSD APIs for THREADS support Message-ID: <200108262010.f7QKA6f28508@arch20m.dellroad.org> In-Reply-To: <3B885ED0.9DFCA5B5@elischer.org> "from Julian Elischer at Aug 25, 2001 07:28:32 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108262010.f7QKA6f28508>