summaryrefslogtreecommitdiffstats
path: root/sys/vm
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2006-05-21 23:25:32 +0000
committerrwatson <rwatson@FreeBSD.org>2006-05-21 23:25:32 +0000
commit09ac5c8c7b98c4b1dceae7668d699c43ed8832dc (patch)
treea21c1048d209330ccc3e20ed4d4765170bafdda5 /sys/vm
parent5eaef84d68a0028a785062a920ad04def809bc92 (diff)
downloadFreeBSD-src-09ac5c8c7b98c4b1dceae7668d699c43ed8832dc.zip
FreeBSD-src-09ac5c8c7b98c4b1dceae7668d699c43ed8832dc.tar.gz
When allocating a bucket to hold a free'd item in UMA fails, don't
report this as an allocation failure for the item type. The failure will be separately recorded with the bucket type. This my eliminate high mbuf allocation failure counts under some circumstances, which can be alarming in appearance, but not actually a problem in practice. MFC after: 2 weeks Reported by: ps, Peter J. Blok <pblok at bsd4all dot org>, OxY <oxy at field dot hu>, Gabor MICSKO <gmicskoa at szintezis dot hu>
Diffstat (limited to 'sys/vm')
-rw-r--r--sys/vm/uma_core.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/sys/vm/uma_core.c b/sys/vm/uma_core.c
index 3268a1c..f08f84d 100644
--- a/sys/vm/uma_core.c
+++ b/sys/vm/uma_core.c
@@ -2413,8 +2413,7 @@ zfree_start:
* If nothing else caught this, we'll just do an internal free.
*/
zfree_internal:
- uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFAIL |
- ZFREE_STATFREE);
+ uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFREE);
return;
}
OpenPOWER on IntegriCloud