public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Re: prctl patch for fpu faults
Date: Wed, 10 Oct 2001 20:26:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805320@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805302@msgid-missing>

>>>>> On Wed, 10 Oct 2001 13:18:38 -0700, "Mallick, Asit K" <asit.k.mallick@intel.com> said:

  Asit> David/Jesse, I would like the default to be noprint. As Jack
  Asit> mentioned that there are applications that will generate lots
  Asit> of these messages. These messages are ok for development
  Asit> systems and debugging applications but for production systems
  Asit> this creates problem. Most of the users want to run the
  Asit> applications (production) that do not require changing the
  Asit> configuration.

It's fine by me if distributors set things up such that they're
disabled by default, but for the kernel I'm releasing, I'll keep them
turned on.  It's just too easy to forget about them otherwise.  And a
program that accidentally generates tons of unaligned faults or fpswa
faults will perform *a lot* worse than a program that occasionally
generates a log message.

  Asit> We have seen people running applications on top of Linux and
  Asit> complaining about the performance compared to other OSes. The
  Asit> performance difference is due to the logging of these
  Asit> messages.

Can you be more specific?  A machine should easily tolerate a rate of
one logged message per second, so if this makes a significant
performance difference, that would be strange.

	--david


  parent reply	other threads:[~2001-10-10 20:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-08 23:42 [Linux-ia64] Re: prctl patch for fpu faults David Mosberger
2001-10-08 23:46 ` Jesse Barnes
2001-10-08 23:54 ` David Mosberger
2001-10-08 23:55 ` Jesse Barnes
2001-10-08 23:57 ` Jesse Barnes
2001-10-09  0:11 ` Jesse Barnes
2001-10-09 21:40 ` Jesse Barnes
2001-10-10 13:59 ` Jack Steiner
2001-10-10 14:18 ` n0ano
2001-10-10 16:34 ` Jesse Barnes
2001-10-10 20:18 ` Mallick, Asit K
2001-10-10 20:26 ` David Mosberger [this message]
2001-10-10 20:42 ` Keith Fish
2001-10-10 22:27 ` David Mosberger
2001-10-10 22:31 ` Jesse Barnes
2001-10-10 22:51 ` David Mosberger
2001-10-10 22:53 ` Khalid Aziz
2001-10-10 22:57 ` Jesse Barnes
2001-10-10 23:05 ` David Mosberger
2001-10-11  3:11 ` Mallick, Asit K
2001-10-11  3:21 ` David Mosberger

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-105590698805320@msgid-missing \
    --to=davidm@hpl.hp.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