Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031643AbXFHVU1 (ORCPT ); Fri, 8 Jun 2007 17:20:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752292AbXFHVUT (ORCPT ); Fri, 8 Jun 2007 17:20:19 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:47964 "EHLO the-village.bc.nu" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752046AbXFHVUS (ORCPT ); Fri, 8 Jun 2007 17:20:18 -0400 Date: Fri, 8 Jun 2007 22:24:37 +0100 From: Alan Cox To: Davide Libenzi Cc: Ulrich Drepper , Theodore Tso , Eric Dumazet , Kyle Moffett , Linux Kernel Mailing List , Linus Torvalds , Andrew Morton , Ingo Molnar Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2 Message-ID: <20070608222437.540bd8a6@the-village.bc.nu> In-Reply-To: References: <466741BD.20106@redhat.com> <20070607110432.73be7960@the-village.bc.nu> <20070607151243.22caab9e.dada1@cosmosbay.com> <466864F8.2050903@cosmosbay.com> <46686810.6030805@redhat.com> <466880A4.3090908@redhat.com> <20070608120746.GD12687@thunk.org> <20070608140150.6f31672f@the-village.bc.nu> <20070608192652.4a291901@the-village.bc.nu> <4669A351.4010403@redhat.com> <20070608203007.3c50eb66@the-village.bc.nu> <20070608204836.5adaefa7@the-village.bc.nu> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.8; i386-redhat-linux-gnu) Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a Lloegr o'r rhif cofrestru 3798903 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1171 Lines: 27 > > #1: Throw the whole thing away and accept its not a good idea anyway > > Unfortunately (exactly because of the same guarantees you're asking for > those handles), in order for userspace libraries to reliably internally > use fds to interact with the kernel, you need another kind of allocation > strategy. Unproven and dubious at best as a claim. > > #2: If I was really going this way and I wanted to use it for serious > > tricks for high performance I/O then I'd provide the handle from > > userspace so that the strategy for allocation is controlled by the caller > > who is the only one who can make the smart decisions > > It does not work. What if the main application, library A and library B > wants to implement their own allocation strategy? Its called "discipline". I would suggest that libc contains a default allocator. You might also want to assign library and application ranges for clarity. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/