From: Thomas Gleixner <tglx@linutronix.de>
To: Tejun Heo <teheo@suse.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: Tue, 3 Aug 2010 13:43:46 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1008031217120.3225@localhost.localdomain> (raw)
In-Reply-To: <4C57D836.1060106@suse.de>
Tejun,
On Tue, 3 Aug 2010, Tejun Heo wrote:
> I agree that timer multiplexing is a rather ugly thing and it would be
> great to remove it. You're right that it doesn't make whole lot of
> difference whether the timer is global or local if it's low frequency
> and in fast paths expect/unexpect would be able to just test its list
> entry and set/clear currently expecting status without messing with
> the global timer or lock. Then, we can have a single low freq timer
> for expect/unexpect and the other for actual polling.
And the third one for watch, right ? That would give us separate timer
functions which each serve a particular purpose.
When you go for it, can you please simplify all the heuristics?
spurious poll:
One fixed poll interval is enough. The retry logic can be made
simple, just set it back to interrupt delivery once per minute and
limit the storm to 10.
watch:
Get rid of the interrupt context work and do all the work in the
timer. Use a fixed interval and either keep it forever or remove it.
expect:
Use a slow fixed interval and just do the expect/unexpect fast
marking. A nice thing would be to have a counter of expect calls so
we can switch off the timer when there is no activity within 10
seconds.
> How does that sound to you?
Way better. :)
Thanks,
tglx
prev parent reply other threads:[~2010-08-03 11:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 13:42 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
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 [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=alpine.LFD.2.00.1008031217120.3225@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=teheo@suse.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
Powered by JetHome