testing IRQL is presumed to be at least as expensive as raising IRQL. If you know the IRQL a priori then take advantage of that. if not then assume the worst case.
that is part of why NDIS passes the knowledge of IRQL level around so that architectures on which it can improve performance have an opportunity to do so.
testing IRQL is for debugging asserts only.
cheers,
dave cattley