DerMixD as a JACK client?

This is mostly about the question of getting several channels from JACK as separate inputs; the question of serving several channels to JACK is basically the same...

I wonder how well the strict treatment of every mono/stereo channel with one thread will scale. Oh, it will be wonderful on a Sun niagara CPU (hm, does it also have that many floating point cores?), but on a normal one-cpu (perhaps dual, quad core) system I wonder how badly the overhead will strike. Having only one CPU, the case of a plain loop over all input channels in order to work out their stuff will most likely be the optimal case.
The multithreading there mostly makes sense for dealing with separate I/O paths to prevent tasks from being held because of other task's data not being there yet. But with JACK, all channels come at once (don't they?).

Is it sensible to cranck up the DerMixD inputs from one or two channels (mono/stereo) to n channels and the according sub-routing?
