Date: Thu, 16 Aug 2007 13:42:58 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Xin LI <delphij@delphij.net> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, David Xu <davidxu@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern kern_thr.c syscalls.master src/sys/sys thr.h Message-ID: <Pine.GSO.4.64.0708161336370.1396@sea.ntplx.net> In-Reply-To: <46C472EF.9070204@delphij.net> References: <200708160526.l7G5Qg0b008022@repoman.freebsd.org> <Pine.GSO.4.64.0708161019000.610@sea.ntplx.net> <46C472EF.9070204@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Aug 2007, Xin LI wrote: > Daniel Eischen wrote: >> On Thu, 16 Aug 2007, David Xu wrote: >> >>> davidxu 2007-08-16 05:26:42 UTC >>> >>> FreeBSD src repository >>> >>> Modified files: >>> sys/kern kern_thr.c syscalls.master >>> sys/sys thr.h >>> Log: >>> Add thr_kill2 syscall which sends a signal to a thread in another >>> process. >> >> I do not think this is a good idea. There is no such thing in Solaris, >> only Linux seems to have this hideous idea of an API. > > I think this would be helpful for applications like Wine. Is there any other > way to implement the semantics? I realize what it's for, and I don't agree that it belongs in the tree. There are other forms of interprocess communication, pipes, sockets, even msg queues. I'm sure you can find a few ways to send a message to a process to say "send signal X to thread Y" if you really wanted to. It looks like even Linux makes you use a thread group, not a thread. I don't see where this was discussed on -arch or -current, but maybe I missed that thread. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0708161336370.1396>