summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_kse.c
diff options
context:
space:
mode:
authorcsjp <csjp@FreeBSD.org>2005-02-24 00:05:50 +0000
committercsjp <csjp@FreeBSD.org>2005-02-24 00:05:50 +0000
commit5e49a0b3963594cfb0bb39292e3cfb709a36ae22 (patch)
tree6d3d3b7ff715e0b9c0c2a37e0ef147f650a20cc5 /sys/kern/kern_kse.c
parenta8e1dad15aaa465e7ebfad55a77a14fc5a8a06b7 (diff)
downloadFreeBSD-src-5e49a0b3963594cfb0bb39292e3cfb709a36ae22.zip
FreeBSD-src-5e49a0b3963594cfb0bb39292e3cfb709a36ae22.tar.gz
Drop bzero and shove the responsibility of zeroing the kse upcall
object on to the zone allocator. It should be noted that uma_zalloc(9) uses bzero to zero out the object so there probably wont be any real performance benefit. If UMA grows the ability to supply zeroed zones more efficiently in the future, we will not have to modify all the existing consumers. Discussed with: rwatson,julian MFC after: 1 week
Diffstat (limited to 'sys/kern/kern_kse.c')
-rw-r--r--sys/kern/kern_kse.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/sys/kern/kern_kse.c b/sys/kern/kern_kse.c
index 4e648f5..ed35902 100644
--- a/sys/kern/kern_kse.c
+++ b/sys/kern/kern_kse.c
@@ -73,8 +73,7 @@ upcall_alloc(void)
{
struct kse_upcall *ku;
- ku = uma_zalloc(upcall_zone, M_WAITOK);
- bzero(ku, sizeof(*ku));
+ ku = uma_zalloc(upcall_zone, M_WAITOK | M_ZERO);
return (ku);
}
OpenPOWER on IntegriCloud