This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
> > Sir; > > i am beginning development of a CAD like program. it will be > threaded and multi-processor capable (well thanks to SMP O/S > like linux). > > as to the linux's memory management, suppose a program has > 30 threads. each thread is allocating and deallocating memory. > > does linux block the other 29 threads when thread <X> wants > to malloc/free? how about other threads/processes in the process > table? > > in a regular, single-processor system, my original C++ program > spent 50% of its time in malloc/free. i reduced this time very > significantly by implementing memory pools. the basic algorithm is fairly > easy to split up across threads. hence linux SMP for more performance. > but i am wondering if i might be walking into a "technical snare" > with respect to linux and memory management. > This has little to do with kernel. I forwarded this to the glibc mailing list. -- H.J. Lu (hjl@gnu.org)
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |