mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Christoph Lameter <cl@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC PATCH] x86-64: software IRQ masking and handling
Date: Sun, 11 Jul 2010 21:26:15 +0200	[thread overview]
Message-ID: <20100711192615.GB21598@elte.hu> (raw)
In-Reply-To: <4C3A06E3.50402@kernel.org>


* Tejun Heo <tj@kernel.org> wrote:

> Hello,
> 
> This is something suggested by Rusty Russell a while ago.  It makes IRQ 
> masking a software switch like preemption or softirq enable/disable.  
> Hardware interrupt masking (cli/sti) and delivery are decoupled from actual 
> IRQ handling.  IRQ disabling is done by single instruction moving 1 to a 
> percpu variable.  Enabling is similar but it should check whether there's 
> any pending interrupt to handle.
> 
> This change greatly reduces the number of hardware IRQ masking 
> manipulations.  cli/sti still being somewhat costly operations (I hear 
> nehalem is better tho), this should be able to improve overall performance, 
> especially on paravirts.

Not just Nehalem but on various AMD CPUs it was in the below-10-cycles range 
for years.

Note that we tried this in -rt, but the pain and trouble (and, often, code 
bloat) was not worth the trouble. The PUSHF/POPF/CLI/STI instructions are 
really simple and short in the instruction stream - without disturbing other 
registers.

	Ingo

  reply	other threads:[~2010-07-11 19:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-11 18:01 Tejun Heo
2010-07-11 19:26 ` Ingo Molnar [this message]
2010-07-11 20:29 ` Linus Torvalds
2010-07-11 22:03   ` Steven Rostedt
2010-07-12  1:18     ` Linus Torvalds
2010-07-12  5:11       ` Eric Dumazet
2010-07-12  8:02         ` Rusty Russell
2010-07-12  7:41       ` Tejun Heo
2010-07-12  2:19   ` Rusty Russell
2010-07-12  2:49     ` Linus Torvalds
2010-07-12  7:45     ` Tejun Heo
2010-07-12  7:35   ` Tejun Heo
2010-07-12 13:55     ` Christoph Lameter
2010-08-03 21:37 ` Jeremy Fitzhardinge
2010-08-04  2:09   ` Rusty Russell

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=20100711192615.GB21598@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cl@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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

all inboxes | Powered by JetHome®