Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 19 Dec 2002 14:31:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 19 Dec 2002 14:31:29 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:39692 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 19 Dec 2002 14:31:28 -0500 Date: Thu, 19 Dec 2002 11:37:06 -0800 (PST) From: Linus Torvalds To: bart@etpmod.phys.tue.nl cc: davej@codemonkey.org.uk, , , , , , , , Subject: Re: Intel P6 vs P7 system call performance In-Reply-To: <20021219135517.7E78051FB6@gum12.etpnet.phys.tue.nl> Message-ID: 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: 1223 Lines: 35 On Thu, 19 Dec 2002 bart@etpmod.phys.tue.nl wrote: > > True, but unless I really don't get it, compatibility of a new static > binary with an old kernel is going to break anyway. NO. The current code in 2.5.x is perfectly able to be 100% compatible with binaries even on old kernels. This whole discussion is _totally_ pointless. I solved all the glibc problems early on, and Uli is already happy with the interfaces, and they work fine for old kernels that don't have a clue about the new system call interfaces. WITHOUT any new magic system calls. WITHOUT any stupid SIGSEGV tricks. WITHOUT and silly mmap()'s on magic files. > My point was that the double-mapped page trick adds no overhead in the > case of a static binary, and just one extra mmap in case of a shared > binary. For _zero_ gain. The jump to the library address has to be indirect anyway, and glibc has several places to put the information without any mmap's or anything like that. 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/