public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org,
	hubicka@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] Start of compat32.h (again)
Date: Thu, 5 Dec 2002 22:21:20 +0100	[thread overview]
Message-ID: <20021205212120.GA1386@elf.ucw.cz> (raw)
In-Reply-To: <20021205.130614.99253893.davem@redhat.com>

Hi!

>    Actually, it tends to nullify the bloat cost and then make it few
>    percent faster... For most of spec2000 modulo two or three cache-bound
>    tests that are 50% slower :-(.
> 
> How about some test where relocations come into play?
> spec2000 is a bad example, it's just crunch code.

time ./configure might be a good test...

> Most systems spend their time running quick small executables over and
> over, and in such cases relocation overhead shows up very strongly.

Really? What workload besides configure does many small programs?

> This is why I asked for fork, exec et al. latency figures for 32-bit
> vs 64-bit on x86_64 but I've been informed in private email that
> nobody can send me numbers due to NDAs.
> 
> I still think making the simple programs like ls, cat, bash et
> al. 64-bit in a dist is a bad idea.

Agreed for ls and cat, but I do not think it hurts for bash...

								Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?

  reply	other threads:[~2002-12-05 21:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0212011047440.12964-100000@home.transmeta.com.suse.lists.linux.kernel>
     [not found] ` <1038804400.4411.4.camel@rth.ninka.net.suse.lists.linux.kernel>
2002-12-02  8:13   ` [PATCH] Start of compat32.h (again) Andi Kleen
2002-12-02  8:28     ` David S. Miller
2002-12-02  9:07       ` Andi Kleen
2002-12-02  9:36         ` Jakub Jelinek
2002-12-02 17:01           ` Mikael Pettersson
2002-12-02 10:16         ` David S. Miller
2002-12-04 11:19           ` Pavel Machek
2002-12-05 21:06             ` David S. Miller
2002-12-05 21:21               ` Pavel Machek [this message]
2002-12-05 21:22                 ` David S. Miller
2002-12-05 21:32                   ` Pavel Machek
2002-11-27  7:42 Stephen Rothwell
2002-11-27  7:58 ` David S. Miller
2002-11-27 13:00   ` Stephen Rothwell
2002-11-28  5:27     ` David S. Miller
2002-11-27 18:51   ` Linus Torvalds
2002-11-28  5:34     ` David S. Miller
2002-11-27  8:00 ` David Mosberger
2002-11-27  8:06   ` David S. Miller
2002-11-27  8:29   ` Andi Kleen
2002-11-27  8:46     ` David Mosberger
2002-11-27  9:01       ` Andi Kleen
2002-11-27  9:57       ` David S. Miller
2002-11-27 17:10         ` David Mosberger
2002-11-28  5:29           ` David S. Miller
2002-11-27 12:49     ` Alan Cox
2002-11-30 20:34     ` Ralf Baechle
2002-11-27 17:18 ` Linus Torvalds
2002-11-28  5:22   ` Stephen Rothwell
2002-11-28  5:26     ` David S. Miller
2002-11-29  2:36       ` Stephen Rothwell
2002-12-01 18:54       ` Linus Torvalds
2002-12-02  4:46         ` David S. Miller
2002-12-02  4:57           ` Stephen Rothwell
2002-12-02  6:17             ` David S. Miller
2002-12-02  7:39           ` Richard Henderson
2002-12-02  7:44             ` David S. Miller
2002-12-02  7:59             ` Ralf Baechle
2002-12-02  8:01               ` David S. Miller
2002-12-04 11:22                 ` Pavel Machek
2002-12-05 21:04                   ` David S. Miller
2002-11-28  5:31   ` David S. Miller

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=20021205212120.GA1386@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=hubicka@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox