Article View: comp.sys.sgi.misc
Article #339Re: memory management in UNIX (SGI IRIX)
From: Patrick Horgan
Date: Mon, 05 Feb 1996 15:06
Date: Mon, 05 Feb 1996 15:06
18 lines
1655 bytes
1655 bytes
It sounds like you have specialized memory management needs that malloc wasn't designed to handle. Writing your own memory management is the way to go. Without knowing more about the behavior of your program I couldn't tell you much more, except that memory management is a well understood subset of computer science with extensive documentation. Many computer science texts in algorithms or operating systems speak extensively on these issues. If you're lucky your memory requests come in fixed sizes for at least a subset of the requests...it's quite efficient to manage pools of fixed size memory. For variable sizes, you'll have to use something like a closest fit with coalescence. Another good source of information are magazines like Dr. Dobbs. I'd bet the Dr. has run at least a couple of articles about memory management a year for years and years. I seem to remember an issue devoted to it within the last couple of years. -- Patrick J. Horgan Broadvision Inc. phorgan@broadvision.com 333 Distel Circle Have horse Phone : (415)943-3677 Los Altos, CA 94022-1404 will ride. FAX : (415)934-3701 Opinions mine, not my employers except by coincidence.
Technical Details
Message-ID:
<4f56dv$r9o@ns.broadvision.com>Path:
arc1-ca.pugleaf.net!nebula.broadvision.com!usenetReferences:
<DM0Jv9.9F4@bii.bruker.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!nebula.broadvision.com!usenet From: phorgan@broadvision.com (Patrick Horgan) Newsgroups: comp.sys.sgi.misc,comp.lang.c,comp.unix.programmer Subject: Re: memory management in UNIX (SGI IRIX) Date: 5 Feb 1996 15:06:39 GMT Organization: The unconfigured xvnews people Message-ID: <4f56dv$r9o@ns.broadvision.com> References: <DM0Jv9.9F4@bii.bruker.com> Reply-To: phorgan@broadvision.com NNTP-Posting-Host: star.broadvision.com