最近学习nginx的源代码,深深地喜欢它的内存池管理方式,一次性申请大块的内存以供分配,避免了小内存的频繁申请释放产生的碎片,而且统一的内存释放可以保证不会有内存泄露。
我在此把nginx的内存池管理代码提取出来方便单独使用。(代码下载地址 http://dl.dbank.com/c0p7h49ts8)
使用方法如下:
#include<iostream>
#include"mem_pool.h"//需要包含此头文件
using namespace std;
int main()
{
mem_pool *pool = mem_create_pool(1024);//创建一个1024字节大小的内存池(不用担心不够用,nginx遇到内存不足时会自己申请足够的内存)
char *mychar = (char *)mem_palloc(pool,100);//请求1:100字节的内存
strcpy(mychar,"use mem_pool to manage your memory 100");
cout << mychar << endl;
mychar = (char *)mem_palloc(pool,300);//请求2:300字节的内存
strcpy(mychar,"use mem_pool to manage your memory 300");
cout << mychar << endl;
mychar = (char *)mem_palloc(pool,1000);//请求3:1000字节的内存
strcpy(mychar,"use mem_pool to manage your memory 1000");
cout << mychar << endl;
int *arr = (int *)mem_palloc(pool,sizeof(int)*4);//请求4:一个整型数组,数组大小自定义为4
arr[0]=3;
arr[1]=4;
arr[2]=5;
arr[3]=6;
printf("%d %d %d %d",arr[0],arr[1],arr[2],arr[3]);
mem_destroy_pool(pool);//统一销毁内存池,不会有内存泄露
return 0;
}
上面我们一共有4次内存申请,由于使用了nginx的内存池,我们通过 valgrind( 一款用于内存调试、内存泄漏检测以及性能分析的软件开发工具)运行程序测试内存分配回收情况
vm6245:/var/samba/mem_pool # g++ test.cpp mem_pool.cpp
vm6245:/var/samba/mem_pool # valgrind ./a.out
==25677== Memcheck, a memory error detector
==25677== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==25677== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==25677== Command: ./a.out
==25677==
use mem_pool to manage your memory 100
use mem_pool to manage your memory 300
use mem_pool to manage your memory 1000
3 4 5 6==25677==
==25677== HEAP SUMMARY:
==25677== in use at exit: 0 bytes in 0 blocks
==25677== total heap usage: 2 allocs, 2 frees, 2,024 bytes allocated
==25677==
==25677== All heap blocks were freed -- no leaks are possible
==25677==
==25677== For counts of detected and suppressed errors, rerun with: -v
==25677== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
我们可以看到nginx内存池 只进行了两次内存申请,并且都得到了释放,没有内存泄露。我们平时做C/C++程序开发最头疼的应该就是内存泄露的问题了吧,多学习一些优秀的开源软件对于内存的管理方式,受益匪浅。