[Nut-upsdev] newhidups and threads (was: suse linux and nut)
Arnaud Quette
aquette.dev at gmail.com
Mon Sep 4 09:34:51 UTC 2006
[moving to upsdev as it's now off topic for upsusers]
2006/8/30, Peter Selinger <selinger at mathstat.dal.ca>:
[snip]
> > the threaded method would allow, with some sub-drv config, to launch
> > the polling thread and/or the interrupt thread. Either feeding the
> > core is not important since the core wouldn't care about that.
>
> I think is may make sense to have a thread for listening on the
> interrupt pipeline, to overcome the problem with synchronous
> communication. But why would you want a thread for features? These
> have to be polled at regular intervals anyway, so this can still be
> done from upsdrv_updateinfo.
that was simply to have a common data processing with 2 feeders, and
to core as the reader/interpreter.
But both methods are good, and I haven't yet had time to investigate
more this problem.
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/
More information about the Nut-upsdev
mailing list