>
>or, (beware, it's going to be ugly), read-only map the task stack's
>lower-4k as lower-4k of the IRQ handler. NOTE, there will be _no_ per-IRQ
>MMU cost with this trick, and it's nice with SMP and threads too.
I have implemented the per-irq thing with the help of mmu to handle
current read only and rw(current) read/write. Booted and worked for some
minutes then the machine locked with high net traffic. It' s too late to
debug that lock now though ;-). Here the pointer if you want to take a
look and give me hints.
ftp://e-mind.com/pub/linux/kernel-patches/irq_stack-1-2.0.115.diff.gz
>_much_ less write-access to 'current->'. (the only write-access from IRQ
>contexts i know of is in update_process_times(), a per-timer-IRQ thing).
I have just triggered the need_resched = 1 (look at the patch).
Andrea[s] Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html