All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: Overhead of highpte
Date: 03 Jul 2003 19:54:05 -0700	[thread overview]
Message-ID: <1057287245.18849.0.camel@nighthawk> (raw)
In-Reply-To: <68160000.1057286782@[10.10.2.4]>

On Thu, 2003-07-03 at 19:46, Martin J. Bligh wrote:
> I suspect the problem is that your gcc is such a slow piece of shit,
> you're totally userspace bound. Try 2.95 (just move the /usr/bin/gcc
> symlink on debian).

Yep, you're right.  I thought I _was_ using 2.95.  Oh well.

-- 
Dave Hansen
haveblue@us.ibm.com


  reply	other threads:[~2003-07-04  2:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 22:53 Overhead of highpte Martin J. Bligh
2003-07-02 23:15 ` William Lee Irwin III
2003-07-03  0:02   ` William Lee Irwin III
2003-07-04  2:34 ` Dave Hansen
2003-07-04  2:46   ` Martin J. Bligh
2003-07-04  2:54     ` Dave Hansen [this message]
2003-07-04  3:53     ` Overhead of highpte (or not :) Dave Hansen

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=1057287245.18849.0.camel@nighthawk \
    --to=haveblue@us.ibm.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=wli@holomorphy.com \
    /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.