Paul Durrant wrote: >> As I hesitate to use non-public interfaces, I will try the taskq >> approach. The documentation does mention limits on the execution time of
Typo: does *NOT* mention limits >> a task within a queue, so it should work. >> > > Yes, I expect taskqs will work for you. As I said though, IMO the > thread interface should be made public. In fact, it would be > interesting to look at what interfaces are commonly used by drivers in > Linux or Windows and make sure Solaris has similar functionality; the > easier porting drivers is, the more people will do it. Our software stack (which actually consists of 6 kernel modules and much userland stuff) uses an internal abstraction layer which makes it possible to keep much of the code generic. This is essential to be able to support Linux, Windows, Solaris and other more exotic OS like HP-UX. The needed functionality actually boils down to maybe 30-40 functions. It does of course help if the kernel APIs (well, some OS don't have such a thing...) match well to keep the required adaption layers thin and simple. Joachim -- Joachim Worringen, Software Architect, Dolphin Interconnect Solutions phone ++49/(0)228/324 08 17 - http://www.dolphinics.com _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
