From owner-freebsd-arch@FreeBSD.ORG Tue Jul 8 06:09:48 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 C01B11065676; Tue, 8 Jul 2008 06:09:48 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 83D438FC1E; Tue, 8 Jul 2008 06:09:48 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.64.3]) by phk.freebsd.dk (Postfix) with ESMTP id 12EF3170E4; Tue, 8 Jul 2008 06:09:47 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m6869kFw000702; Tue, 8 Jul 2008 06:09:46 GMT (envelope-from phk@critter.freebsd.dk) To: Sergey Babkin From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 07 Jul 2008 16:56:33 EST." <29793635.342951215467793639.JavaMail.root@vms126.mailsrvcs.net> Date: Tue, 08 Jul 2008 06:09:46 +0000 Message-ID: <701.1215497386@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: arch@FreeBSD.org, Robert Watson Subject: 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: Tue, 08 Jul 2008 06:09:48 -0000 In message <29793635.342951215467793639.JavaMail.root@vms126.mailsrvcs.net>, Se rgey Babkin writes: >>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. What you're proposing to do in the kernel isn't any less complicated :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.