From: linas@austin.ibm.com (Linas Vepstas)
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackeras <paulus@samba.org>,
Arnd Bergmann <arnd.bergmann@de.ibm.com>,
Olaf Hering <olh@suse.de>
Subject: Re: [PATCH] remove bogomips from /proc/cpuinfo
Date: Mon, 31 Jul 2006 13:57:02 -0500 [thread overview]
Message-ID: <20060731185702.GF4453@austin.ibm.com> (raw)
In-Reply-To: <jewt9tfxlq.fsf@sykes.suse.de>
On Mon, Jul 31, 2006 at 08:17:05PM +0200, Andreas Schwab wrote:
> Olaf Hering <olh@suse.de> writes:
>
> > On Mon, Jul 31, Arnd Bergmann wrote:
> >
> >> On Monday 31 July 2006 14:59, Olaf Hering wrote:
> >> > Remove bogomips from /proc/cpuinfo.
> >> > It is now really bogus since "timebase-frequency" is shown.
> >>
> >> Well, but it's still part of the ABI, right?
> >> How do you determine that there are no broken applications
> >> still relying on it?
> >
> > Everything works on a G5, as example. Alpha doesnt have it either.
> > What pratical value had bogomips for an application?
>
> What harm does it do?
Kernel bloat.
--linas
prev parent reply other threads:[~2006-07-31 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 12:59 [PATCH] remove bogomips from /proc/cpuinfo Olaf Hering
2006-07-31 17:46 ` Arnd Bergmann
2006-07-31 17:49 ` Olaf Hering
2006-07-31 18:17 ` Andreas Schwab
2006-07-31 18:57 ` Linas Vepstas [this message]
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=20060731185702.GF4453@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=arnd.bergmann@de.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
--cc=paulus@samba.org \
--cc=schwab@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).