From owner-freebsd-arch@FreeBSD.ORG Mon Jul 7 21:57:01 2008 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B11601065691; Mon, 7 Jul 2008 21:57:01 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.freebsd.org (Postfix) with ESMTP id 91E7F8FC0C; Mon, 7 Jul 2008 21:57:01 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms126.mailsrvcs.net ([172.18.12.131]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K3N00EI6OY9EH70@vms046.mailsrvcs.net>; Mon, 07 Jul 2008 16:56:33 -0500 (CDT) Received: from 65.242.108.162 ([65.242.108.162]) by vms126.mailsrvcs.net (Verizon Webmail) with HTTP; Mon, 07 Jul 2008 16:56:33 -0500 (CDT) Date: Mon, 07 Jul 2008 16:56:33 -0500 (CDT) From: Sergey Babkin X-Originating-IP: [65.242.108.162] To: Sergey Babkin , Poul-Henning Kamp Message-id: <29793635.342951215467793639.JavaMail.root@vms126.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit Cc: arch@FreeBSD.org, Robert Watson Subject: Re: Re: Proposal: a revoke() system call X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 21:57:01 -0000 >From: Poul-Henning Kamp >If the only reason we are dicussing this, is that people find the >magic pipe to select ugly, then I would even argue that we have not >reached critical mass for even thinking. Well, there are a couple of problems with magical pipes: 1. It means using 3 times as many file descriptors. (One for the original socket, and 2 for the ends of the pipe). 2. When working with the 3rd-party libraries, it requires a substantial rework of these libraries. Getting a file decriptor from inside the library's implementation and forcing it to close is a lot less invasive and can be done with a simple API wrapper. -SB