Scott Ullrich wrote:
On Tue, Nov 10, 2009 at 1:50 AM, Lenny <five2one.le...@gmail.com> wrote:
Lenny wrote:
Scott Ullrich wrote:
On Mon, Nov 9, 2009 at 3:45 PM, Scott Ullrich <sullr...@gmail.com> wrote:
Contact me off list. I have a kernel I need you to test.
In the meantime, please try increasing these sysctl's:
pfSense:~# sysctl -a | grep rx_processing_limit
dev.em.0.rx_processing_limit: 100
dev.em.1.rx_processing_limit: 100
dev.em.2.rx_processing_limit: 100
dev.em.3.rx_processing_limit: 100
Try increasing each to 256, then 512, 1024, 2048, etc.
If these do not help contact me for a new kernel.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
Hi Scott,
Actually, I have them set on a 1000 for quite a while now. Before I did that
I had errors on interfaces. Do you still want me to increase to 2048 and
more?
Thanks,
Lenny.
At second thought, to get rid of the errors I told you about, I did 2
things:
added this to /boot/loader.conf:
hw.em.rxd="4096"
hw.em.txd="4096"
and added to /etc/sysctl.conf:
dev.em.0.rx_processing_limit=1000
dev.em.1.rx_processing_limit=1000
plus, I changed
net.inet.ip.intr_queue_maxlen=4096
and added
kern.ipc.somaxconn=1024
These were the changes I did outside of the WebGUI.
So should I still increase the dev.em.X.rx_processing_limit value?
Also let me know what this sysctl is showing:
net.inet.ip.intr_queue_drops
If it shows >0 then you might want to increase net.inet.ip.intr_queue_maxlen
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
it's 0.
Lenny.
