Re: question concerning proper usage of kernel variables net.bpf.bufsize and vm_kmem_size_max
- From: "R. B. Rid***" <arne_woerner@xxxxxxxxx>
- Date: Wed, 26 Jul 2006 00:27:53 -0700 (PDT)
--- Raymond Owens <owensr@xxxxxxxxxxx> wrote:
Questions:No, but you could set it with this procedure:
Can VM_KMEM_SIZE_MAX be set manually with sysctl?
1. Insert the lines
vm.kmem_size=123456789
vm.kmem_size_max=1234567890
in
/boot/loader.conf
2. reboot
That should change those values...
(see src/sys/kern/kern_malloc.c)
I wonder, why your box needs such a big buffer? Do u have network traffic
bursts or so?
-Arne
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
freebsd-performance@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "freebsd-performance-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: question concerning proper usage of kernel variables net.bpf.bufsize and vm_kmem_size_max
- From: Jin Guojun [VFFS]
- Re: question concerning proper usage of kernel variables net.bpf.bufsize and vm_kmem_size_max
- References:
- Prev by Date: question concerning proper usage of kernel variables net.bpf.bufsize and vm_kmem_size_max
- Next by Date: Re: question concerning proper usage of kernel variables net.bpf.bufsize and vm_kmem_size_max
- Previous by thread: question concerning proper usage of kernel variables net.bpf.bufsize and vm_kmem_size_max
- Next by thread: Re: question concerning proper usage of kernel variables net.bpf.bufsize and vm_kmem_size_max
- Index(es):