On 26 Nov 2004 at 11:46, Joachim Van der Auwera wrote:
As the thing will be called in supervisor mode itself, it could just keep track of some "ready for use" channels which are then passed to the device driver when needed. Then the problem is fully solved. The thing itself checks whether there are still enough "waiting devices" and allocates new devices in user mode which are queued for use by the device (in supervisor mode).
There's something I don't understand. When will the thing allocate devices in
user mode?
Perhaps we can agree that a thing never does any...thing by itself. The only
time something is achieved with a thing is when a JOB calls the thing's use
routine. Then that thing use routine is executed as if it was part of the
job's code.
To allocate new devices in user mode a job would have to call the thing in
user mode, and we're back to the beginning (at least I think we are).
Wolfgang
Perhaps the best solution (?) would be for the FILTER THING to maintain a user defineable number of open channels (say 5?) - it would open them all at initialisation. Then when a filter program is launched to deal with the data contained within one of the open channels, it could tell the FILTER THING (in user mode) to open another one ready...
How memory hungry would this be
-- Rich Mellor RWAP Services 26 Oak Road, Shelfield, Walsall, West Midlands WS4 1RQ
http://www.rwapservices.co.uk/
_______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
