mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Zachary Amsden <zach@vmware.com>
Cc: linux-kernel@vger.kernel.org, davej@codemonkey.org.uk, hpa@zytor.com
Subject: Re: [PATCH] faster signal handling on x86
Date: Tue, 26 Oct 2004 16:15:00 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0410261610380.28839@ppc970.osdl.org> (raw)
In-Reply-To: <417EC7BA.3050604@vmware.com>



On Tue, 26 Oct 2004, Zachary Amsden wrote:
>
> I noticed an unneeded write to dr7 in the signal handling path for x86.  
> We only need to write to dr7 if there is a breakpoint to re-enable, and 
> MOVDR is a serializing instruction, which is expensive.  Getting rid of 
> it gets a 33% faster signal delivery path (at least on Xeon - I didn't 
> test other CPUs, so your gain may vary).

I'm suprised it is _that_ slow, but sure, no problem, the patch just makes 
it match all the other paths. 

I suspect Xeon is alone in being _that_ slow - I bet Netburst flushes the 
whole trace cache on db7 writes.

		Linus

      reply	other threads:[~2004-10-26 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 21:55 Zachary Amsden
2004-10-26 23:15 ` Linus Torvalds [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=Pine.LNX.4.58.0410261610380.28839@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=davej@codemonkey.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zach@vmware.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

all inboxes | Powered by JetHome®