Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756788AbXFIRA5 (ORCPT ); Sat, 9 Jun 2007 13:00:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753957AbXFIRAu (ORCPT ); Sat, 9 Jun 2007 13:00:50 -0400 Received: from x35.xmailserver.org ([64.71.152.41]:4093 "EHLO x35.xmailserver.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754202AbXFIRAt (ORCPT ); Sat, 9 Jun 2007 13:00:49 -0400 X-AuthUser: davidel@xmailserver.org Date: Sat, 9 Jun 2007 10:00:44 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@alien.or.mcafeemobile.com To: Paul Mackerras cc: Alan Cox , Theodore Tso , Ulrich Drepper , Eric Dumazet , Kyle Moffett , Linux Kernel Mailing List , Linus Torvalds , Andrew Morton , Ingo Molnar Subject: Re: [patch 7/8] fdmap v2 - implement sys_socket2 In-Reply-To: <18026.15766.574693.200636@cargo.ozlabs.ibm.com> Message-ID: 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> <18026.15766.574693.200636@cargo.ozlabs.ibm.com> X-GPG-FINGRPRINT: CFAE 5BEE FD36 F65E E640 56FE 0974 BF23 270F 474E X-GPG-PUBLIC_KEY: http://www.xmailserver.org/davidel.asc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1175 Lines: 29 On Sat, 9 Jun 2007, Paul Mackerras wrote: > Davide Libenzi writes: > > > The only reason we use a floating base, is because Uli preferred to have > > non-exactly predictable fd allocations. There no reason of re-doing the > > same POSIX mistake all over again: > > Why must everything that makes things a bit simpler and more > predictable for application programmers be called a "mistake"? Because if you give guarantees on something, ppl start using such guarantee in the wrong way. Kyle's email summarizes it. This should really be treated as an opaque handle, with no assumption on its value. And if you start handing over values that are not predictable, the userspace is *forced* to not use any assumption on its values. I never made any assumption on values returned by APIs returning "handles", and I never had any problem (or even care) about how those values were distributed in the N bit space. - Davide - 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/