Re: Broken IPsec + enc +pf/ipfw

2014-10-23 Thread Andrey V. Elsukov
On 22.10.2014 23:28, Matthew Grooms wrote: > On 10/21/2014 1:39 PM, Kyle Williams wrote: >> On Tue Oct 21 11:35:15 2014, Matthew Grooms wrote: >>> Hey Kyle, >>> >>> Thanks for lending a hand. I tested a few myself last night but had no >>> luck. This morning I received an email off list that pointe

What a reason to run /sbin/atmconfig diag list in /etc/network.subr?

2014-10-23 Thread Oleg Ginzburg
Getting the issue when i run a certain number of vnet-epair-jail described in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194550 I could not understand why in /etc/network.subr execute atm-case from afexists() function and in particular, why we need to run /sbin/atmconfig diag list 2>/dev

Re: Broken IPsec + enc +pf/ipfw

2014-10-23 Thread Matthew Grooms
On 10/23/2014 5:56 AM, Andrey V. Elsukov wrote: On 22.10.2014 23:28, Matthew Grooms wrote: On 10/21/2014 1:39 PM, Kyle Williams wrote: On Tue Oct 21 11:35:15 2014, Matthew Grooms wrote: Hey Kyle, Thanks for lending a hand. I tested a few myself last night but had no luck. This morning I recei

[Bug 183659] [tcp] TCP stack lock contention with short-lived connections

2014-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183659 John Baldwin changed: What|Removed |Added Status|Needs MFC |In Discussion CC|

[Bug 183659] [tcp] TCP stack lock contention with short-lived connections

2014-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183659 John Baldwin changed: What|Removed |Added Assignee|freebsd-net@FreeBSD.org |j...@freebsd.org -- You are receiv

Re: ixgbe(4) spin lock held too long

2014-10-23 Thread Jason Wolfe
On Sat, Oct 18, 2014 at 4:42 AM, John Baldwin wrote: > On Friday, October 17, 2014 11:32:13 PM Jason Wolfe wrote: >> Producing 10G of random traffic against a server with this assertion >> added took about 2 hours to panic, so if it turns out we need anything >> further it should be pretty quick.

[Bug 193053] ixgbe(4) IXGBE_LEGACY_TX + ALTQ path broken

2014-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193053 ncrog...@gmail.com changed: What|Removed |Added Version|9.2-STABLE |10.1-RC2 -- You are receiving

[Bug 194234] [ixgbe] Update ixgbe to 2.5.27

2014-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194234 Eric Joyner changed: What|Removed |Added Attachment #148084|0 |1 is obsolete|

[Bug 194234] [ixgbe] Update ixgbe to 2.5.27

2014-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194234 Eric Joyner changed: What|Removed |Added Attachment #148085|0 |1 is obsolete|

[Bug 194234] [ixgbe] Update ixgbe to 2.5.27

2014-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194234 --- Comment #6 from Eric Joyner --- I've attached two updated patches, in svn diff format. The shared code patch is just a more recent version of the previous one I submitted; still more updates to prepare for support for new adapters. Th

[Bug 194234] [ixgbe] Update ixgbe to 2.5.27

2014-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194234 Adrian Chadd changed: What|Removed |Added CC||adr...@freebsd.org --- Comment #7 f

nd6_timer vs Giant vs locking in general

2014-10-23 Thread Mateusz Guzik
Hello there, dtrace revealed that the kernel schedules nd6_timer a lot. Not only that, his callout is not mpsafe so the kernel locks Giant which I believe is an oversight. Also the code looks really suspicious as it walks V_in6_ifaddrhead without any locking (not to mention there is an interestng