lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 7 Jun 2011 09:59:20 +0300
From:	Pekka Enberg <>
Cc:	Ingo Molnar <>, Andrew Lutomirski <>,, Thomas Gleixner <>,, Jesper Juhl <>,
	Borislav Petkov <>,
	Linus Torvalds <>,
	Andrew Morton <>,
	Arjan van de Ven <>,
	Jan Beulich <>,
	richard -rw- weinberger <>,
	Mikael Pettersson <>,
	Andi Kleen <>,
	Brian Gerst <>,
	Louis Rilling <>,
Subject: Re: [PATCH v5 8/9] x86-64: Emulate legacy vsyscalls

On Tue, Jun 7, 2011 at 1:49 AM,  <> wrote:
>> A fastpath is defined by optimization considerations applied to a
>> codepath (the priority it gets compared to other codepaths), *not* by
>> its absolute performance.
> we're not talking about random arbitrarily defined paths here but the
> impact of putting well predicted branches into the pf handler vs. int xx
> (are you perhaps confused by 'fast path' vs. 'fastpath'?).

Well, I'm sure confused by 'fast path' vs 'fastpath'! Can you please
explain the difference? Thanks!

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists