summaryrefslogtreecommitdiff
path: root/Porting/findvars
diff options
context:
space:
mode:
authorNicholas Clark <nick@ccl4.org>2010-09-08 10:24:04 +0100
committerNicholas Clark <nick@ccl4.org>2010-09-08 10:24:04 +0100
commit9a87bd09eea1d037e82e99f6ece528e39e7fe0e6 (patch)
tree687527f4f2be761e544a22f09e7bbd4ee0a51141 /Porting/findvars
parentea25a9b2cf73948b1e8c5675de027e0ad13277bd (diff)
downloadperl-9a87bd09eea1d037e82e99f6ece528e39e7fe0e6.tar.gz
Remove offer_nice_chunk(), PL_nice_chunk and PL_nice_chunk_size.
These provided a non-public API for the hash and array code to donate free memory direct to the SV head allocation routines, instead of returning it to the malloc system with free(). I assume that on some older mallocs this could offer significant benefits. However, my benchmarking on a modern malloc couldn't detect any significant effect (positive or negative) on removing the code. Its (continued) presence, however, has downsides a: slightly more code complexity b: slightly larger interpreter structure c: in the steady state, if net creation of SVs is zero, 1 chunk of allocated but unused memory will exist (per thread) So I think it best to remove it.
Diffstat (limited to 'Porting/findvars')
-rw-r--r--Porting/findvars2
1 files changed, 0 insertions, 2 deletions
diff --git a/Porting/findvars b/Porting/findvars
index b2914f5652..173175e14e 100644
--- a/Porting/findvars
+++ b/Porting/findvars
@@ -204,8 +204,6 @@ na
nexttoke
nexttype
nextval
-nice_chunk
-nice_chunk_size
ninterps
nomemok
numeric_local