Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752647AbXFDFMM (ORCPT ); Mon, 4 Jun 2007 01:12:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751538AbXFDFL7 (ORCPT ); Mon, 4 Jun 2007 01:11:59 -0400 Received: from smtp1.linux-foundation.org ([207.189.120.13]:51511 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750792AbXFDFL6 (ORCPT ); Mon, 4 Jun 2007 01:11:58 -0400 Date: Sun, 3 Jun 2007 22:11:28 -0700 (PDT) From: Linus Torvalds To: Davide Libenzi cc: Ulrich Drepper , Linux Kernel Mailing List , Andrew Morton , Ingo Molnar Subject: Re: [patch 2/2] ufd v1 - use unsequential O(1) fdmap In-Reply-To: Message-ID: References: <4663067C.9050002@redhat.com> <466319DB.80800@redhat.com> 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: 833 Lines: 20 On Sun, 3 Jun 2007, Davide Libenzi wrote: > > Agreed, a new syscall looks less messy. I'll make sys_dup2() to allow > installing in the non-sequential area, only if there's an fd already > allocated. F_DUPFD will remain unchanged (that is, not allow > non-sequential fds allocations). I actually think that a new system call is _hugely_ messy. It means that anybody who wants to use a new feature needs to have a new glibc. Not nice, not nice at all. I'd much rather see a totally transparent extension that doesn't require any new user space what-so-ever to be used... Linus - 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/