···136136 If we were to preallocate them for the 128TB of user virtual address137137 space, we would need to reserve 512TB+2GB, which is larger than the138138 entire virtual address space today. This means they can not be reserved139139- ahead of time. Also, a single process's pre-popualated bounds directory139139+ ahead of time. Also, a single process's pre-populated bounds directory140140 consumes 2GB of virtual *AND* physical memory. IOW, it's completely141141 infeasible to prepopulate bounds directories.142142···151151 these calls.152152153153Q: Could a bounds fault be handed to userspace and the tables allocated154154- there in a signal handler intead of in the kernel?154154+ there in a signal handler instead of in the kernel?155155A: mmap() is not on the list of safe async handler functions and even156156 if mmap() would work it still requires locking or nasty tricks to157157 keep track of the allocation state there.