From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] platform hook for timer_interrupt()
Date: Wed, 03 Sep 2003 22:10:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106262716804346@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106261055215953@msgid-missing>
On Wed, Sep 03, 2003 at 07:49:18PM +0100, Matthew Wilcox wrote:
> How about smp_call_function() in a regular timer then?
smp_call_function() is kind of messy since it uses IPI to call
on each CPU. Not sure that's a good solution since it won't complete
until all the CPUs have executed the given function.
If kernel threads or tasklets don't cut it, I could understand why
using a timers machvec would be "lighter weight".
grant
next prev parent reply other threads:[~2003-09-03 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 17:19 [patch] platform hook for timer_interrupt() Matthew Wilcox
2003-09-03 17:33 ` Alex Williamson
2003-09-03 17:33 ` Martin Hicks
2003-09-03 18:49 ` Matthew Wilcox
2003-09-03 22:10 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-03 16:42 Martin Hicks
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=marc-linux-ia64-106262716804346@msgid-missing \
--to=iod00d@hp.com \
--cc=linux-ia64@vger.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