From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] New CMC/CPE polling
Date: Mon, 04 Aug 2003 18:26:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106002225806115@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105969308328993@msgid-missing>
> Here's a redesign of the CMC and CPE polling for both 2.6.0-test2
> and 2.4.21. This is roughly the same design I requested comment on
> a while back (BTW, nobody commented...). Basically, rather than
> flooding all the cpus in parallel, I used some low priority interrupts
> to cascade through the cpus. This should be much more scalable. I
> also added a new feature of enabling interrupts for the CMC and CPE
> handlers. The SAL spec claims these functions are SMP safe and
> re-entrant and even recommends that the corrected error handlers
> should run with interrupts enabled. It works on HP boxes, others
> might want to double check that their firmware adheres to the spec.
> The combination of these things should keep polling from impacting
> system response time. I tried to keep the 2.6 and 2.4 code as similar
> as possible, so I also backported __ffs() to 2.4. Feedback and bug
> reports welcome. Thanks,
I think that there are some race conditions around the setting/clearing
of cmc_polling_enabled.
-Tony
next prev parent reply other threads:[~2003-08-04 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 23:06 [PATCH] New CMC/CPE polling Alex Williamson
2003-08-01 6:34 ` David Mosberger
2003-08-01 14:20 ` Alex Williamson
2003-08-04 18:26 ` Luck, Tony [this message]
2003-08-04 18:49 ` Alex Williamson
2003-08-04 20:43 ` Luck, Tony
2003-08-04 21:15 ` Alex Williamson
2003-08-04 21:53 ` Luck, Tony
2003-08-04 23:09 ` David Mosberger
2003-08-08 18:39 ` Bjorn Helgaas
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-106002225806115@msgid-missing \
--to=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.