Some thoughts:
1. I really don't like hardirq/UP ... it's like old cli()/sti() days
2. For hardirq/SMP, "hurt-ness" will depend also on APIC "routing", or no?
Maybe I'm just TOO strong about soft-bh-semantics "matched" by soft-locking
and leaving hardirq semantics for lower levels that require interaction with
hardware.
For example, ipchains (ip_fw.c) uses hardirq locking around lookup loops
that seem quite long given that we are in bh context.
... and still wondering about Alan's tests for 2.1 irq latency.
Regards.
-- -- Juanjo http://juanjox.home.ml.org/
- 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