[Autogenerated] the virtual APIs are the most powerful that we
have in user mode because they're closest to the memory manager
functions such as virtual dialogue,
varchar free varchar protect and some others are some of these APIs you
might find that family specifically the mutual I'll KPI is going to call
the function anti allocate mutual memory,
which is the native API The system called that actually goes on into
the kernel and asked the manager to perform the operations we require
because this function is so close to the memory manager and the
memory manager always works in terms of pages so do these APIs So the
virtual APIs always work in page boundaries and always round up to
page sizes.
This is the only perhaps of these APIs in cases where you need smaller
allocations or occasions that not necessarily our page size aligned.
However, if this is what you need,
you need big allocations then the virtual API is the
most efficient and the best one to use,
it allows us to do anything that is possible to do with memory,
including reserving memory, not just committing memory,
changing memory protection, locking memory and so on.
So these are obviously the most powerful ones and and so that
would be or should be your first choice unless there's some
other concerns that you have,
especially if you need to allocate small memory chunks in that
case you're probably better off using the hip APIs Let's see an
example of utilizing the mutual APIs