public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Nottingham <notting@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] New Red Hat Linux Beta release for ia64 availabl e
Date: Tue, 01 May 2001 19:55:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005506@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205864@msgid-missing>

McCaffity, Ray (ray.mccaffity@wcg.com) said: 
> 1. I know with all the hub-bub surrounding BogoMips the last few years on
> the x86
>    platforms, the number doesn't mean a whole lot.  But I still use it as a
> "close-enough"
>    baseline for some of my servers.  Anyway, the output from cat
> /proc/cpuinfo is
>    slightly different from the bogoMips in the dmesg.  Which one is more
> reliable?

They should be resonably similar, although they might vary slightly
between processors.

> 2. For my 733Mhz IA64's, my BogoMips is around 730, which is slower than 1
> bogo per
>    MHz.  This is a long way from what I get with x86 processors.

That's irrelevant.

>    if I go too far the server starts getting unstable.  What are the number
> of
>    file handles supported by Linux 2.4.x ?

It's settable in proc. See Documentation/sysctl.

Bill


  parent reply	other threads:[~2001-05-01 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-19 17:04 [Linux-ia64] New Red Hat Linux Beta Release for IA-64 available Bill Nottingham
2001-04-27 22:09 ` [Linux-ia64] New Red Hat Linux Beta release for ia64 available Bill Nottingham
2001-05-01 19:47 ` [Linux-ia64] New Red Hat Linux Beta release for ia64 availabl McCaffity, Ray
2001-05-01 19:55 ` Bill Nottingham [this message]
2001-05-01 20:42 ` [Linux-ia64] New Red Hat Linux Beta release for ia64 availabl e Don Dugger

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=marc-linux-ia64-105590693005506@msgid-missing \
    --to=notting@redhat.com \
    --cc=linux-ia64@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