Date: Tue, 7 Nov 2000 23:02:05 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: jadream <jadream@chat.ru> Cc: freebsd-questions@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: Is msgrcv() thread-blocking in 4.x? Message-ID: <20001107230204.Q5112@fw.wintelcom.net> In-Reply-To: <20001106015047.Q5112@fw.wintelcom.net>; from bright@wintelcom.net on Mon, Nov 06, 2000 at 01:50:48AM -0800 References: <3A0667ED.B3074BF6@chat.ru> <20001106015047.Q5112@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Alfred Perlstein <bright@wintelcom.net> [001106 01:51] wrote: > * jadream <jadream@chat.ru> [001106 00:11] wrote: > > Hi ppl! > > > > I have two processes both multithreaded with threads from one process > > comunicating with threads from another using SystemV IPC (msgs & > > semaphores). > > That used to work well under Linux as threads there are just same as > > processes. > > But when I came to the process-limit in Linux and had to change for > > freeBSD all comes bad. > > msgrcv() and semop() are blocking whole processes not appropriate > > threads and I'm near the point of blowing up. Updated patch is here: http://people.freebsd.org/~alfred/uthread_sysvipc.diff it's for releng4, it makes the FreeBSD threads library poll on the semaphores and msgqueues, not very good, but if/when I get a chance I may try to hook kqueue into some of the sysv IPC stuff so that we don't need to poll the primatives. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001107230204.Q5112>