James Simmons wrote:
> I agree. I think the best way is to create a struct mem_locks that has a
> linked list of locks to test and a field to discribe what card is using
> mmio thats mmapped to user space. Place this in the task_struct. In the
> schedular test to see if mem_lock is their then see if its lock by another
> process. If it is then skip picking this process.

Hmm, why even bother with a quick hack that has no chance of ever
being included into the kernel? If a driver needs to arbitrate access
to it's hardware it's the driver's job to deal with that.

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan/
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: [EMAIL PROTECTED]

Reply via email to