uvm_mem_mam request/reserve region size

Is there some good reason that the n_bytes argument to uvm_mem_mam request_region() and reserve_region() are unsigned ints and not unsigned longints?

It seems inconsistent with the address "offset" arguments/attributes which *are* longints (or bit [63:0]) and obviously it prevents allocation of regions larger than 2**32-1.

Perhaps this could/should be fixed in a future release?

Or is there some subtlety I'm missing.

Thanks.

Walker