Posted Aug 5, 2009 14:56 UTC (Wed) by corbet
In reply to: kmap_atomic
Parent article: The realtime preemption endgame
That wouldn't quite do it - you still have to avoid contention for the atomic kmap slots or chaos will result. That generally implies disabling preemption, which is what they're trying to avoid. I suppose one could implement some sort of slot-management layer so that one task's KM_USER0 is different from another's, but that sounds messy...
to post comments)