28.08.2019 3:20, Victor Gamov wrote:
hw.igb.max_interrupt_rate=32000
>>>
>>> It's about 5000-7000 per rxq
>>
>> 7000 is quite close considering it is average for quite long period (a
>> second or seconds).
>> It can hit 8000 for some ticks easily in your case.
>
> Eugene, can you explain
28.08.2019 3:59, Victor Gamov wrote:
>>> sysctl.conf
>>> =
>>> net.link.ether.ipfw=1
>>> net.link.bridge.ipfw=1
>>> net.link.bridge.ipfw_arp=1
>>> net.link.bridge.pfil_member=1
>>>
>>> net.inet.ip.fw.verbose_limit=100
>>> net.inet.ip.fw.verbose=1
>>> =
>> Do you really use ipfw filtering
On 27/08/2019 23:30, Eugene Grosbein wrote:
28.08.2019 2:20, Victor Gamov wrote:
sysctl.conf
=
net.link.ether.ipfw=1
net.link.bridge.ipfw=1
net.link.bridge.ipfw_arp=1
net.link.bridge.pfil_member=1
net.inet.ip.fw.verbose_limit=100
net.inet.ip.fw.verbose=1
=
You should avoid passing
28.08.2019 2:20, Victor Gamov wrote:
>> Victor, do you have some non-default tuning in your /boot/loader.conf or
>> /etc/sysctl.conf?
>> If yes, could you show them?
> Nothing special.
>
> loader.conf
> =
> machdep.hyperthreading_allowed="0"
> net.inet.ip.fw.default_to_accept=1
> =
>
On 27/08/2019 22:59, Eugene Grosbein wrote:
28.08.2019 2:22, Victor Gamov wrote:
Also, you should monitor interrupt numbers shown by "systat -vm 3" for igb*
devices
at hours of most load. If they approach 8000 limit but not exceed it,
you may be suffering from this and should raise the limit
28.08.2019 2:22, Victor Gamov wrote:
>> Also, you should monitor interrupt numbers shown by "systat -vm 3" for igb*
>> devices
>> at hours of most load. If they approach 8000 limit but not exceed it,
>> you may be suffering from this and should raise the limit with
>> /boot/loader.conf:
>>
>>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724
John Delano changed:
What|Removed |Added
CC||webmas...@rgcwireless.com
---
On 27/08/2019 21:50, Eugene Grosbein wrote:
28.08.2019 1:46, Eugene Grosbein wrote:
28.08.2019 1:03, Andrey V. Elsukov wrote:
As you can see, when ipfw produces high load, interrupt column is more
than system.
Interrupt numbers higher than others generally mean that traffic is processed
On 27/08/2019 21:46, Eugene Grosbein wrote:
28.08.2019 1:03, Andrey V. Elsukov wrote:
As you can see, when ipfw produces high load, interrupt column is more
than system.
Interrupt numbers higher than others generally mean that traffic is processed
without netisr queueing mostly.
That is
28.08.2019 1:46, Eugene Grosbein wrote:
> 28.08.2019 1:03, Andrey V. Elsukov wrote:
>
>> As you can see, when ipfw produces high load, interrupt column is more
>> than system.
>
> Interrupt numbers higher than others generally mean that traffic is processed
> without netisr queueing mostly.
>
On 27/08/2019 21:03, Andrey V. Elsukov wrote:
On 26.08.2019 19:25, Victor Gamov wrote:
More general question about my current config. I have about 200Mbit
input multicasts which bridged and filtered later (about 380 Mbit
bridged if trafshow does not lie me :-) )
My FreeBSD box (12.0-STABLE
On 26.08.2019 19:25, Victor Gamov wrote:
> More general question about my current config. I have about 200Mbit
> input multicasts which bridged and filtered later (about 380 Mbit
> bridged if trafshow does not lie me :-) )
>
> My FreeBSD box (12.0-STABLE r348449 GENERIC amd64) has one
On 26/08/2019 20:15, Eugene Grosbein wrote:
26.08.2019 23:25, Victor Gamov wrote:
More general question about my current config. I have about
200Mbit input multicasts which bridged and filtered later (about
380 Mbit bridged if trafshow does not lie me :-) )
Don't trust trafshow. Use: systat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #3 from John Delano ---
I have discovered that if I unplug the ethernet cable, ifconfig still shows the
cable is "status: active"!
FreeBSD 11 immediately goes to "status: no carrier" when I do the same.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
John Delano changed:
What|Removed |Added
CC||webmas...@rgcwireless.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240144
--- Comment #1 from Aleks ---
work
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239982
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Keywords|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238796
Kubilay Kocak changed:
What|Removed |Added
Flags|mfc-stable11?, |mfc-stable11+,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240023
Kubilay Kocak changed:
What|Removed |Added
See Also||https://github.com/luigiriz
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240144
Kubilay Kocak changed:
What|Removed |Added
Product|Ports & Packages|Base System
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240144
Kubilay Kocak changed:
What|Removed |Added
Hardware|Any |amd64
--
You are receiving this
21 matches
Mail list logo
