Yes...
The idea is that quark could by calling this function pre-empt the driver from checking the limit. I thought this was necessary since some of the checks could be expensive given the information that the driver knows but cheaper if quark did it. But since the unoptimized driver knows what quark knows (since that's how it seems to have been modeled) it's not needed. So remove it? I kept the quotas stuff separate in case I need to.