[openib-general] [ANNOUNCE] Initial trunk checkin of ISERinitiator

[Guy]

guy> Isn’t there a problem with polling for CQ, from the CQ’s upcall 
guy> context (i.e. potentially tasklet/interrupt context).

I would like to address this question again to the list, with hope
to get a couple of things clarified.

How much is linux tolerant to code making *long* use of the interrupt
context. Are there any limitations (set by the kernel hackers)
regarding this issue ? (I know that in rtos this is totally not
acceptable, for understandable reasons)

How long does count as *long* ? Is it measured in jiffies/usecs/locs
other ?

Our iser implementation is currently context switching the completion
(interrupt context) to a kernel thread for the "handling" and the rest
of the polling. But, if linux tolerants code in isr contexts we might
consider changing that (at least for the initiator code).

Any help in clearing that up, would be much appreciated.

Thanks,
Guy.

p.s.
in the request_irq call (mthca_eq.c) - why not set the SA_SAMPLE_RANDOM
to contribute to the linux entropy pool ?