All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Katz <katzj@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: RE: 46% performance drop with change in glibc
Date: Tue, 08 Nov 2005 21:02:17 -0500	[thread overview]
Message-ID: <1131501737.3533.28.camel@bree.local.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E82A@liverpoolst.ad.cl.cam.ac.uk>

On Tue, 2005-11-08 at 13:17 +0000, Ian Pratt wrote:
>  > >It should be in the main tree. The appended patch was included some 
> > >time ago, but I've never tested it to see whether it works since I 
> > >don't generally run bleeding edge Fedora.
> > >
> > >Is there some piece of the patch missing?
> > >
> > No, it's all there.  Only part I needed was the change to 
> > ld.so.conf.  
> > So, anyone with FC4, you might want to make sure you have the 
> > entry "hwcap 0 nosegneg".  It looks like the performance 
> > regression has disappeared now.  Thanks all for you help.
> 
> Perhaps we should have the install script insert a file called
> /etc/ld.so.conf.d/xen containing "hwcap 0 nosegneg" ?

Sounds sane.  As Uli said, this mirrors what happens when our xen kernel
package is installed.

Jeremy

  parent reply	other threads:[~2005-11-09  2:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 13:17 46% performance drop with change in glibc Ian Pratt
2005-11-08 14:57 ` Andrew Theurer
2005-11-08 16:53   ` Ulrich Drepper
2005-11-08 19:30   ` Kurt Garloff
2005-11-09  2:02 ` Jeremy Katz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-07 21:26 Ian Pratt
2005-11-08 13:05 ` Andrew Theurer
2005-11-04 16:08 Ian Pratt
2005-11-07 21:09 ` Andrew Theurer
2005-11-02 19:10 Andrew Theurer
2005-11-02 19:17 ` Kip Macy
2005-11-02 19:23   ` Andrew Theurer
2005-11-02 20:14     ` Andrew Theurer
2005-11-02 21:31       ` Ulrich Drepper
2005-11-02 20:37 ` Anthony Liguori

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=1131501737.3533.28.camel@bree.local.net \
    --to=katzj@redhat.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.