From: Gregory Maxwell <greg@linuxpower.cx>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
"David S. Miller" <davem@redhat.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: X15 alpha release: as fast as TUX but in user space (fwd)
Date: Sun, 29 Apr 2001 16:18:27 -0400 [thread overview]
Message-ID: <20010429161827.B17539@xi.linuxpower.cx> (raw)
In-Reply-To: <Pine.LNX.4.33.0104281752290.10866-100000@localhost.localdomain> <20010428215301.A1052@gruyere.muc.suse.de> <200104282256.f3SMuRW15999@vindaloo.ras.ucalgary.ca> <9cg7t7$gbt$1@cesium.transmeta.com> <3AEBF782.1911EDD2@mandrakesoft.com> <15083.64180.314190.500961@pizda.ninka.net> <20010429153229.L679@nightmaster.csn.tu-chemnitz.de> <200104291848.f3TIm6821037@vindaloo.ras.ucalgary.ca> <20010429221159.U706@nightmaster.csn.tu-chemnitz.de>
In-Reply-To: <20010429221159.U706@nightmaster.csn.tu-chemnitz.de>; from ingo.oeser@informatik.tu-chemnitz.de on Sun, Apr 29, 2001 at 10:11:59PM +0200
On Sun, Apr 29, 2001 at 10:11:59PM +0200, Ingo Oeser wrote:
[snip]
> The point is: The code in that "magic page" that considers the
> tradeoff is KERNEL code, which is designed to care about such
> trade-offs for that machine. Glibc never knows this stuff and
> shouldn't, because it is already bloated.
>
> We get the full win here, for our "compile the kernel for THIS
> machine to get maximum performance"-strategy.
>
> People tend to compile the kernel, but not the glibc.
>
> Just let the benchmarks, Linus and Ulrich decide ;-)
The kernel can even customize the page at runtime if it needs to, such as
changing algorithims to deal with lock contention.
Of course, this page will need to present a stable interface to glibc, and
having both the code and a comprehensive jump-table might become tough in a
single page...
next prev parent reply other threads:[~2001-04-29 20:18 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 15:52 X15 alpha release: as fast as TUX but in user space (fwd) Ingo Molnar
2001-04-28 19:53 ` Andi Kleen
2001-04-28 22:56 ` Richard Gooch
2001-04-29 5:13 ` H. Peter Anvin
2001-04-29 11:14 ` Jeff Garzik
2001-04-29 11:27 ` David S. Miller
2001-04-29 13:32 ` Ingo Oeser
2001-04-29 18:48 ` Richard Gooch
2001-04-29 18:55 ` Gregory Maxwell
2001-04-29 19:02 ` Richard Gooch
2001-04-29 19:47 ` Gregory Maxwell
2001-04-29 19:54 ` Richard Gooch
2001-04-29 20:11 ` Ingo Oeser
2001-04-29 20:18 ` Gregory Maxwell [this message]
2001-04-29 22:20 ` Richard Gooch
2001-04-30 0:13 ` Andrea Arcangeli
2001-04-29 20:45 ` Arjan van de Ven
2001-04-29 22:18 ` Richard Gooch
2001-04-30 16:46 ` Alan Cox
2001-04-29 19:38 ` Jamie Lokier
2001-04-29 23:53 ` Andrea Arcangeli
2001-04-29 16:21 ` dean gaudet
2001-04-29 20:19 ` H. Peter Anvin
2001-04-29 22:29 ` Richard Gooch
2001-04-29 21:16 ` Jim Gettys
2001-04-29 21:40 ` H. Peter Anvin
2001-04-29 21:47 ` Jim Gettys
2001-05-02 18:18 ` Matti Aarnio
2001-05-02 19:34 ` Linus Torvalds
2001-05-02 20:55 ` Fabio Riccardi
2001-04-30 7:02 ` David S. Miller
2001-04-30 7:29 ` H. Peter Anvin
2001-04-30 7:51 ` David S. Miller
2001-04-30 14:56 ` Jonathan Lundell
2001-04-30 8:42 ` Pavel Machek
2001-05-03 7:13 ` Kai Henningsen
2001-05-03 7:44 ` Keith Owens
2001-05-03 10:37 ` Ingo Oeser
2001-05-03 15:44 ` Gregory Maxwell
2001-05-07 19:04 ` Pavel Machek
2001-05-03 9:37 ` Alan Cox
2001-05-07 19:03 ` vsyscalls [was Re: X15 alpha release: as fast as TUX but in user space (fwd)] Pavel Machek
2001-05-03 12:23 ` X15 alpha release: as fast as TUX but in user space (fwd) Helge Hafting
2001-05-03 19:09 ` Pavel Machek
2001-05-03 19:50 ` agrawal
2001-05-07 19:07 ` vsyscallRe: " Pavel Machek
2001-05-03 20:19 ` Alan Cox
2001-05-03 20:41 ` Gregory Maxwell
2001-05-04 8:06 ` Pavel Machek
2001-05-04 17:31 ` dean gaudet
2001-05-04 8:43 ` bert hubert
2001-05-02 10:52 ` Andi Kleen
2001-05-02 10:53 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010429161827.B17539@xi.linuxpower.cx \
--to=greg@linuxpower.cx \
--cc=davem@redhat.com \
--cc=hpa@zytor.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.