Jiacheng asked about disabling interrupts for a long time (600-700usecs) and whether it was OK; also that there was a high priority interrupt that can take 600-700 usecs. I (possibly) mistakenly answered; I was only thinking about disabling interrupts at task level and not considering a high priority interrupt that could interrupt the nimble stack during either a radio or timer isr.
I would have to take a closer look at the current code to see if the stack could handle a higher priority interrupt that interrupts either the cputime isr or the radio isr. I believe it can but it was not considered when the code was written so there may be catastrophic failures. Just wanted to make folks aware of this. I also presume that folks thinks that the controller should be written in such a way that developers can have higher priority interrupts enabled than the radio/timer isrs? Of course, this could always interfere with radio timing and BLE events; the idea being that nothing catastrophic happens. This would not add a lot of code and should not add much time to existing interrupts.
