You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The memory allocation interface(s) allow the allocation of physical pages at runtime, as well as for the management of memory mappings in the instance's / thread's address space.
These are particularly sensitive to design given a few considerations:
Port buffers must work with these
"Priority" allocations, such as DMA memory regions
Physical allocation checks during mapping
Avoiding exposing direct paddrs to the userspace processes (security concern)
Further, given the kernel avoids working with any linear data (except in the case of ports) much of this must be performed in "constant space" via the ABI.
The text was updated successfully, but these errors were encountered:
The memory allocation interface(s) allow the allocation of physical pages at runtime, as well as for the management of memory mappings in the instance's / thread's address space.
These are particularly sensitive to design given a few considerations:
Further, given the kernel avoids working with any linear data (except in the case of ports) much of this must be performed in "constant space" via the ABI.
The text was updated successfully, but these errors were encountered: