From owner-freebsd-hackers Thu Nov 9 13:36:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.west.se (unknown [194.52.130.37]) by hub.freebsd.org (Postfix) with ESMTP id 94E3437B4C5 for ; Thu, 9 Nov 2000 13:36:40 -0800 (PST) Received: from west.se (bashful [192.168.0.14]) by mail.west.se (8.11.0/8.9.3) with ESMTP id eA9FbxH71867 for ; Thu, 9 Nov 2000 16:37:59 +0100 (CET) (envelope-from bjorn.tornqvist@west.se) Message-ID: <3A0AC4FB.DEE94ED9@west.se> Date: Thu, 09 Nov 2000 16:38:35 +0100 From: Bjorn Tornqvist Organization: West AB X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-BETA i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Modifying msgrcv() and msgsnd() Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm going to add 2 functioncalls to the kernel; msgrcv_t() msgsnd_t() ("t" as in timeout) where the user will be able to specify a maximum amount of time they are prepared to wait for a message to be sent or become available. I just wonder if the rest of the freebsd community is interested in these kinds of additions to the kernel? I'm pretty certain there is alot more people out there who'd like this functionality. Should I bother posting them to the list? As a sidenote: The main reason I need this is since I can't use longjmp()/setjmp() with alarm() between pthread contexts; with FreeBSD 5.0 this fix probably won't be necessary (but still nice to have though). And besides, I'd get paid to contribute to the project! =) Greetings, Bjorn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message