From: Tejun Heo <teheo@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Greg KH <gregkh@suse.de>
Subject: Re: [GIT PULL tip/genirq] Please pull from lost-spurious-irq
Date: Mon, 02 Aug 2010 17:35:35 +0200 [thread overview]
Message-ID: <4C56E5C7.90206@suse.de> (raw)
In-Reply-To: <4C56E42D.5010300@suse.de>
On 08/02/2010 05:28 PM, Tejun Heo wrote:
> The reason why poll_irq() looks complicated is because different types
> of timers on the same desc shares the timer. The reason why it's
> shared this way instead of across different descs of the same type is
> to avoid locking overhead in maintaining the timer and linked lists of
> its targets. By sharing the timer in the same desc, everything can be
> protected by desc->lock but if we use timers across different descs,
> we need another layer of locking.
Ooh, another reason is timer locality. If timers are shared per desc,
they have much higher chance of being on the same processor. Global
timers would be pretty bad in that respect.
--
tejun
next prev parent reply other threads:[~2010-08-02 15:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 13:42 [GIT PULL tip/genirq] Please pull from lost-spurious-irq Tejun Heo
2010-07-28 13:46 ` Tejun Heo
2010-07-29 8:44 ` Thomas Gleixner
2010-07-30 9:46 ` Tejun Heo
2010-08-02 14:07 ` Thomas Gleixner
2010-08-02 15:28 ` Tejun Heo
2010-08-02 15:35 ` Tejun Heo [this message]
2010-08-02 18:52 ` Thomas Gleixner
2010-08-02 19:57 ` Tejun Heo
2010-08-03 10:06 ` Thomas Gleixner
2010-08-03 10:15 ` Tejun Heo
2010-08-02 21:06 ` Tejun Heo
2010-08-02 21:51 ` Thomas Gleixner
2010-08-02 17:10 ` Thomas Gleixner
2010-08-02 20:48 ` Tejun Heo
2010-08-02 22:28 ` Thomas Gleixner
2010-08-03 8:49 ` Tejun Heo
2010-08-03 11:43 ` Thomas Gleixner
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=4C56E5C7.90206@suse.de \
--to=teheo@suse.de \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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