From owner-freebsd-hackers Mon Mar 6 6:17:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw-out.comptel.com (mgw-out.comptel.com [195.237.145.101]) by hub.freebsd.org (Postfix) with ESMTP id B9DDA37B723 for ; Mon, 6 Mar 2000 06:17:23 -0800 (PST) (envelope-from stefan.parvu@comptel.com) Received: from ctlfw1 ([195.237.145.97]) by mgw-out.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 6 Mar 2000 16:17:10 +0200 Received: from mgw-in.comptel.com ([192.102.20.150]) by ctlfw1.comptel.com; Mon, 06 Mar 2000 16:15:59 +0000 (EET) Received: from comptel.com ([195.237.135.174]) by mgw-in.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 6 Mar 2000 16:17:09 +0200 Message-ID: <38C3BE39.36CDDA55@comptel.com> Date: Mon, 06 Mar 2000 16:18:33 +0200 From: stefan parvu Reply-To: stefan.parvu@comptel.com Organization: Comptel PLC X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Titus von Boxberg Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Pthread blocking I/O References: <38C3BF60.55CF16CC@schuett-inhouse.de> 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 have not so much experience using POSIX threads, but we had in university a project and for I/O to use threads is not so good method. You slow down the process. Some comments? Isn't so? stefan Titus von Boxberg wrote: > > Hi, > > I use two threads to do I/O for a process. > The I/O takes place either on a socket or > an I/O device (com port) file descriptor. > > Apparently it is not possible to shutdown those > threads from a third thread, neither using close nor shutdown(2) for > the socket I/O if the threads are blocked during read. > > What methods can one use to unblock such a blocked-on-read > thread? > > Thanks, > > TITUS > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message