1.Now, you might think that this would cause problems for programs calling malloc -- how do they know about this struct?
现在，您可能会认为当程序调用malloc时这会引发问题——它们如何知道这个结构？
2.If you need 15 bytes, ask for 15 bytes; don't round it up to 32 bytes or some other bigger chunk like you used to do when you used malloc.
如果你需要15个字节，它就请求15个字节；不要像使用malloc的时候那样进位到32个字节或者更大的块大小。
3.It is possible for malloc to overcommit, and some other process may get the resource before the current process, resulting in a failure.
malloc可能会过量分配内存，其他进程可能在当前进程之前获得资源，这会导致错误。
4.malloc_init is going to be our function to initialize our memory allocator.
malloc_init将是初始化内存分配程序的函数。
5.If the user needs to track malloc and free calls in a particular user function, the malloc. d script can be modified as shown below.
如果用户需要跟踪某个用户函数中的malloc和free调用，那么可以按以下方式修改malloc.d脚本。
6.Since the session is a malloc'd object, we also have to free the session when we're done with it.
因为这个会话是一个malloc过的对象，所以我们在使用完它时还必须将其释放。
7.These three keywords are to the stack segment just as "malloc" and "dealloc" are to the heap segment . . . unnecessary.
这三个关键字之于栈，就像是“malloc”和“dealloc”之于堆……多余。
8.You add the stack_depth: 3 parameter to limit the stack trace collected when a malloc is called.
添加stack_depth：3参数，限制调用malloc时收集的栈跟踪。
9.Since a single heap is actually pided into many heaps (up to 32), unnecessary enabling of malloc multiheap can cause severe fragmentation.
因为单一堆实际上被分割为许多个堆（最多32个），不必要地启用mallocmultiheap会导致严重的碎片化。
10.Watson malloc: This new malloc subysystem handles small requests more quickly over the default implementation of memory fragmentation.
Watsonmalloc：与内存碎片的缺省实现相比，这种新的malloc子系统能够快速处理一些小的请求。