summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/malloc.c
Commit message (Collapse)AuthorAgeFilesLines
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Back out previous commit after discussing it with Dmitrij Tejblum.des1999-07-071-4/+0
|
* Always set errno to ENOMEM when returning 0 from malloc() or realloc().des1999-07-071-1/+5
| | | | Approved by: phk
* Disable the "Hint" option in phkmalloc as default. Recent VM systemphk1999-03-281-2/+2
| | | | | | | | | | | | changes have made this too expensive. This gains about 1.25% on worldstone on my SMP machine. Swap-less machines, for instance PicoBSDs, and machines which experience page-out trafic, check with top(1), will probably want to reenable this with: ln -s H /etc/malloc.conf Suggested by: alc (&dyson ?)
* Delete the XXX comments that refer to spinlock recursion. The malloc/free/jb1998-09-301-15/+1
| | | | | | | | | realloc functions check for recursion within the malloc code itself. In a thread-safe library, the single spinlock ensures that no two threads go inside the protected code at the same time. The thread implementation is responsible for ensuring that the spinlock does in fact protect malloc. There was a window of opportunity in which this was not the case. I'll fix that with a commit RSN.
* Use 8k pagesize on alpha, not 4k.dfr1998-09-231-1/+5
|
* Back out part of previous commit (even though it's technically correct).alex1998-09-201-1/+17
| | | | | | | | | | | Our spinlock implementation allows a particular thread to obtain a lock multiple times, but release the lock with a single unlock call. Since we're detecting recursion, we know the lock is already owned by the current thread in a previous call and must not be released in the current call. This is really far too dependent on this particular spinlock implementation, so I've added commented out calls to THREAD_UNLOCK in the appropriate places. We can activate this code when spinlock is taught to count each lock operation.
* Correctly back out of free if a recursive call into malloc.c is detected.alex1998-09-191-8/+7
| | | | | | Set malloc_func *after* grabbing the thread lock. Noticed by: Simon Coggins <simon@oz.org>
* preserve errno across the readlink() calls. There is no value in trashingpeter1998-06-181-1/+4
| | | | errno during a successful malloc() call.
* Add support for thread lock debug. No impact of the malloc code.jb1998-06-091-4/+4
|
* Replace the threaded locking with spinlock calls for both threadedjb1998-04-291-18/+10
| | | | | | | and non-threaded programs. This makes malloc thread safe for linking with libpthread and kernel threads. Reviewed by: phk
* Change in name of the static initializer define.jb1998-04-041-2/+2
|
* NetBSD doesn't have a utrace syscall, so don't define that ifjb1998-03-091-2/+4
| | | | __NETBSD_SYSCALLS is defined.
* Drop the use of caddr_t in conjunction with mmap(2).alex1997-12-311-4/+4
|
* Fix recursion problem which occurs when a signal is received duringjb1997-12-151-3/+12
| | | | | | | a malloc. The signal handler creates a thread which requires a malloc... For now, the only thing to do is to block signals. When we move user pthreads to use the kernel threads, mutexes will be implemented in kernel space and then malloc can revert.
* Another 32bits of 64bits conformance.phk1997-08-311-2/+2
| | | | | Reviewed by: phk Submitted by: jdp
* Improvement of type independency for the bitmap.phk1997-08-271-3/+4
| | | | | | | This makes 64bit operation more likely. Reviewed by: phk Submitted by: jdp
* Malloc option H is now default.phk1997-08-271-2/+2
|
* Fix a minor typo. It only affects the sparc version.jdp1997-07-261-2/+2
|
* Have another go at the malloc-sysv initialization.phk1997-07-021-12/+11
| | | | | PR: 4002 Pointed out by: bde
* malloc_sysv used before initialized, reported in PR4002 byphk1997-07-011-33/+19
| | | | | | | | | | | | | | | Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru> Various cleanup from Keith Bostic Reinstate calloc() as a separate funtion, in its own source/object file. leave the manpage integrated with malloc.3 and friends. Too many things were broken in this respect. PR: 4002 Reviewed by: phk Submitted by: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru> Submitted by: Keith Bostic <bostic@bostic.com>
* Integrate calloc with the rest of the gang.phk1997-06-221-150/+93
| | | | | | | | | | | Various portability and stylistic cleanups. Kill MALLOC_STATS & the 'D' option. Fix the 'V' option. Major overhaul of the man-page. You milage should not vary. Reviewed by: Keith Bostic <bostic@bostic.com> Submitted by: Keith Bostic <bostic@bostic.com>
* Add yet an option, this time on how to deal with malloc(0) and realloc(ptr.0)phk1997-06-121-5/+9
| | | | Prompted by: X11 & XFree86
* Fix mutex initialization.jb1997-06-041-6/+4
| | | | | | | | | | | | | Malloc cannot use pthread_mutex_init() to initialize a mutex because the mutex initialization process does a malloc! libc_r internals skip the malloc and assign an initializer to a static structure and point the opaque type (pthread_mutex_t in this case) to that structure. This is done on the assumption that the mutex will never be destroyed. This style of initialization is only valid inside libc_r because the structure that is assigned is opaque to the user. This fix allows a simple program to get to main() again. 8-)
* Malloc flag X makes malloc behave like the canonical xmalloc() wrapper.phk1997-05-301-18/+56
| | | | | | | Untested support for Solaris from John-Mark Gurney Reviewed by: phk Submitted by: (partially) John-Mark Gurney <gurney_j@resnet.uoregon.edu>
* Check for overflow in size argument.phk1997-03-181-2/+4
| | | | | Tested by: Joel Maslak <j@pobox.com> Closes: PR kern/2964
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* _thread_kern_sig_unblock takes an integer, not a reference.alex1996-12-291-2/+2
| | | | Submitted by: John Birrell <jb@cimlogic.com.au>
* If you run with option Z and malloc fails, memset gets calledphk1996-10-291-4/+6
| | | | | | | with a NULL pointer (archie) Explain that minsize is also the smallest alignment. Submitted by: Archie Cobbs <archie@whistle.com>
* Various cosmeticsphk1996-10-261-48/+28
| | | | | | Improve chances of troublefree 64bit operation. [imp] Noticed by: Warner Losh <imp@village.org>
* malloc_pages should be static.phk1996-10-201-187/+103
| | | | | | | | | | | | | | | | Add progname to warning/error message layout. (joerg) Remove inline assembler, no speed impact, not need for the obfuscation (bde) Remove on the fly calculation of parameters, no longer critical. Make D & U flags valid even if we don't support them. Don't call imalloc until we're done initializing. Zap contents on free() if we have "Junk" set. [*] Various nitpicking. [*] As a sideeffect of this change, if you are worried about sensitive data lingering in memory, you can use the 'Junk' option now to make sure phkmalloc zaps memory when it is returned. add char * malloc_options = "J"; to your source. Obviously there is a performance impact.
* Fix a typo.sos1996-09-251-2/+2
| | | | Reviewed by: phk
* A number of minor bogons and portability things from jdp.phk1996-09-251-28/+37
| | | | Submitted by: jdp
* phkmalloc/3phk1996-09-231-189/+232
| | | | | | | | Various neat features added. More documentation in the manpage. If your machine has very little RAM, I guess that would be < 16M these days :-(, you may want to try this: ln -fs 'H<' /etc/malloc.conf check the manpage.
* Fix a very rare error condition: The code to free VM back to the kernelphk1996-09-171-3/+4
| | | | | | | as done after a quasi-recursive call to free() had modified what we thought we knew about the last chunk of pages. This bug manifested itself when I did a "make obj" from src/usr.sbin/lpr, then make would coredump in the lpd directory.
* Isolated all the crap for thread-safe so I can see what goes on again...phk1996-07-031-61/+48
|
* Reviewed by: julian and (hsu?)julian1996-01-221-3/+66
| | | | | | Submitted by: John Birrel(L?) changes for threadsafe operations
* Fix a fencepost error.phk1996-01-051-4/+4
| | | | Found by: Lars Fredriksen <fredriks@mcs.com>
* Preallocate a small structure, so we can sbrk(2) further back.phk1995-12-181-2/+8
| | | | | Reviewed by: phk Submitted by: Kaleb Keithly <kaleb@x.org>
* Change phkmalloc so that the page directory is now floating and allocatedpeter1995-12-111-29/+47
| | | | | | | | | | | | | | | | | | | | | via mmap() up around the shared library area. Previously the directory was allocated from space from it's own memory pool. Because of the way it was being extended on processes with large malloced data segments (ie: inn) once the page directory was extended for some reason, it was not possible to lower the heap size any more to return pages to the OS. (If my understanding is correct, page directory expansion occurs at 4MB, 12MB, 20MB, 28MB, etc.) I was seeing INN allocate a large amount of short term memory, pushing it over the 28MB mark, and once it's transient demands hit 28MB, it never freed it's pages and swap space again.) I've been running this in my libc for about a month... Also, seperate MALLOC_STATS from EXTRA_SANITY.. I found it useful to call malloc_dump() from within INN from a ctlinnd command to see where the hell all the memory was going.. :-) I've left MALLOC_STATS enabled, as it has no run-time or data storage cost. Reviewed by: phk
* Remove EXTRA_SANITY, fix a unused var.phk1995-10-221-4/+8
|
* phkmalloc/2phk1995-10-081-291/+353
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "zero' and 'junk' options to help find and diagnose malloc abuse. EXTRA_SANITY defaults "junk" to on. Don't dump the internal state, unless EXTRA_SANITY. General code cleanup. Error messages cleaned up a bit, more checking earlier. EXTRA_SANITY is default at this time (just in case). Performance (without EXTRA_SANITY) is better, beats gnumalloc in both time & space most of the time: # In-memory test. ./malloc 50000000 2000 8192 159.2u 1.5s 2:41.85 99.3% 5+7742k 0+0io 0pf+0w ./gnumalloc 50000000 2000 8192 272.6u 0.4s 4:35.01 99.3% 5+8533k 0+0io 0pf+0w # Swap-space test. ./malloc 500000 14000 8192 6.5u 4.1s 4:08.87 4.3% 5+49209k 0+0io 9772pf+0w ./gnumalloc 500000 14000 8192 16.2u 14.5s 15:36.14 3.2% 5+54100k 0+0io 47651pf+0w # Small items test. ./malloc 20000000 20000 2048 67.0u 0.3s 1:07.83 99.2% 5+18199k 0+0io 4pf+0w ./gnumalloc 20000000 20000 2048 66.2u 0.3s 1:07.03 99.3% 5+18107k 0+0io 0pf+0w SANITY is not an option anymore. (!!)
* A buglet when dumping and a stylistic point from Mike.phk1995-09-221-8/+8
| | | | Submitted by: Mike Pritchard <mpp@mpp.minn.net>
* ``phkmalloc''phk1995-09-161-361/+1006
| | | | | | | Performance is comparable to gnumalloc if you have sufficient RAM, and it screams around it if you don't. Compiled with "EXTRA_SANITY" until further notice. see malloc.3 for more details.
* Remove trailing whitespace.rgrimes1995-05-301-6/+6
|
* BSD 4.4 Lite Lib Sourcesrgrimes1994-05-271-0/+420
OpenPOWER on IntegriCloud