Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 19 Dec 2002 13:38:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 19 Dec 2002 13:38:36 -0500 Received: from server.ehost4u.biz ([209.51.155.18]:11220 "EHLO host.ehost4u.biz") by vger.kernel.org with ESMTP id ; Thu, 19 Dec 2002 13:38:35 -0500 Message-ID: <1040323590.3e0214063a990@209.51.155.18> Date: Thu, 19 Dec 2002 13:46:30 -0500 From: billyrose@billyrose.net To: bart@etpmod.phys.tue.nl Cc: root@chaos.analogic.com, linux-kernel@vger.kernel.org Subject: Re: Intel P6 vs P7 system call performance MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 65.132.64.69 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.ehost4u.biz X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [32001 32001] / [32001 32001] X-AntiAbuse: Sender Address Domain - host.ehost4u.biz Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 719 Lines: 22 > Not true. A ret(urn) is (sort of) equivalent to 'pop %eip'. The above > code would actually jump to address 0xfffff000, but probably be slow > since it confuses the branch prediction. > > >Bart that being the case, then the original code that Linus put forth: pushl $0xfffff000 call *(%esp) add $4,%esp would be the way to go as it is highly readable. actually, the code at 0xfffff000 could issue a ret $4 and eliminate the add after the call. - 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/