Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S288984AbSAZCPx>; Fri, 25 Jan 2002 21:15:53 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S288985AbSAZCPm>; Fri, 25 Jan 2002 21:15:42 -0500
Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:27911 "EHLO
	neon-gw.transmeta.com") by vger.kernel.org with ESMTP
	id <S288984AbSAZCPj>; Fri, 25 Jan 2002 21:15:39 -0500
Date: Fri, 25 Jan 2002 18:14:25 -0800 (PST)
From: Linus Torvalds <torvalds@transmeta.com>
To: Andi Kleen <ak@suse.de>
cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] syscall latency improvement #1
In-Reply-To: <20020126030341.A9651@wotan.suse.de>
Message-ID: <Pine.LNX.4.33.0201251810270.16989-100000@penguin.transmeta.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


On Sat, 26 Jan 2002, Andi Kleen wrote:
> On Fri, Jan 25, 2002 at 05:53:57PM -0800, Linus Torvalds wrote:
> >
> > On 26 Jan 2002, Andi Kleen wrote:
> > >
> > > It doesn't explain the Athlon speedups. On athlon cli is ~4 cycles.
> >
> > .. and it probably serializes the instruction stream.
>
> I have word from AMD engineering that it doesn't stall the pipeline
> or serializes.

Note that it may not be the "cli" itself - the "iret" may be slower if it
has to enable interrupts that were disabled before. Ie the iret microcode
may have the equivalent of

	/* Did eflags change? */
	if ((new_eflags ^ old_eflags) & IF_MASK)
		.. do sti/cli as appropriate ..

which would mean that the "cli" itself may take 4 cycles, but the "sti"
implicit in the iret will _also_ take 4 cycles and is optimized away when
not needed.

Which would add up to the 8 cycles needed for a ~3.4% speedup (this is
assuming the baseline is something like 250 cycles per system call, I've
not checked that assumption).

		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/