From: "Doug Thompson" <dthompson@lnxi.com>
To: <arjan@infradead.org>
Cc: <bluesmoke-devel@lists.sourceforge.net>, <dsp@llnl.gov>,
<hch@lst.de>, <alan@lxorguk.ukuu.org.uk>, <akpm@osdl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/15] EDAC: switch to kthread_ API
Date: Fri, 03 Mar 2006 08:57:46 -0700 [thread overview]
Message-ID: <4408050A0200003600000CC8@zoot.lnxi.com> (raw)
Originally we used a timeout, but when I added the PCI Parity scanning,
that broke while trying to get a PCI spinlock (via a PCI API call)
during the timer interrupt time. I then added the current kernel thread
model and a first attempt. We subsequently received input for the
kthread_* model which is were this patch came from.
Currently the timer event code performs two operations:
1) ECC polling and
2) PCI parity polling.
I want to split those from each other, so each can have a seperate cycle
rate (also adding a sysfs cycle control for the PCI parity timing in
addition to the existing ECC cycle control).
One of the thoughts I have had in this refactoring is to utilize worker
queue processing to do the work (and bypass the spinlock issue) which is
triggered by the timer event for PCI parity polling and thus also the
ECC polling for uniformity.
Thoughts are welcome
doug thompson
On Fri, 2006-03-03 at 09:16 +0000, Arjan van de Ven wrote:
> On Thu, 2006-03-02 at 18:30 -0800, Andrew Morton wrote:
> > Dave Peterson <dsp@llnl.gov> wrote:
> > >
> > > schedule_timeout((HZ * poll_msec) / 1000);
> > > try_to_freeze();
> > > + __set_current_state(TASK_RUNNING);
> >
> > schedule() and schedule_timeout*() always return in state TASK_RUNNING, so
> > I'll take that out of there.
> >
> > We might as well use schedule_timeout_interruptible(), too. As a bonus, we
> > get to delete that spelling mistake ;)
>
>
> or even msleep variant ;)
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> bluesmoke-devel mailing list
> bluesmoke-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel
next reply other threads:[~2006-03-03 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 15:57 Doug Thompson [this message]
2006-03-03 23:20 ` Dave Peterson
2006-03-04 0:03 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 1:47 Dave Peterson
2006-03-03 2:30 ` Andrew Morton
2006-03-03 9:16 ` Arjan van de Ven
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=4408050A0200003600000CC8@zoot.lnxi.com \
--to=dthompson@lnxi.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dsp@llnl.gov \
--cc=hch@lst.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®