From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: levon@movementarian.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /proc/sys/kernel/pointer_size
Date: Wed, 08 Jan 2003 15:03:03 -0800 (PST) [thread overview]
Message-ID: <20030108.150303.130044451.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301081502270.7688-100000@penguin.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Wed, 8 Jan 2003 15:04:05 -0800 (PST)
System binaries match the kernel. It's as easy as that. So what if 90% of
the user binaries use 32-bit mode because it's smaller and faster? We're
talking about a system binary that is _very_ intimate with the kernel.
oprofile can perfectly legitimately be used to monitor 32-bit binaries
running on under a 64-bit kernel environment. In fact I expect such
exercises to be very instructive. Anton Blanchard has done this
already on ppc64.
And being that 64-bit sparc systems run several orders of magnitude
faster than 32-bit ones, I think I'd prefer to oprofile 32-bit
programs on sparc64 boxes :-)
Hey, if this is so distasteful we could just add a
sys_kernel_pointer_size() to sparc64 and ppc64 and be done with it.
The other choice, as mentioned, is to make every platform use u64's
in the tables.
next prev parent reply other threads:[~2003-01-08 23:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 19:59 [PATCH] /proc/sys/kernel/pointer_size John Levon
2003-01-08 20:28 ` Linus Torvalds
2003-01-08 20:52 ` John Levon
2003-01-08 21:03 ` Linus Torvalds
2003-01-08 22:37 ` David S. Miller
2003-01-08 22:40 ` John Levon
2003-01-11 9:18 ` Kai Henningsen
2003-01-08 22:34 ` David S. Miller
2003-01-08 23:04 ` Linus Torvalds
2003-01-08 23:03 ` David S. Miller [this message]
2003-01-09 0:02 ` Linus Torvalds
2003-01-09 0:03 ` David S. Miller
2003-01-09 4:00 ` Daniel Jacobowitz
2003-01-09 4:31 ` David S. Miller
2003-01-09 5:23 ` William Lee Irwin III
2003-01-09 23:09 ` Bill Davidsen
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=20030108.150303.130044451.davem@redhat.com \
--to=davem@redhat.com \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox