libmap32.conf on stable/11

2016-09-01 Thread Slawa Olhovchenkov
libmap32.conf missing on 11.0-STABLE. still present in `man libmap.conf` etcupdate remove existing libmap32.conf ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebs

Re: X2APIC support

2016-09-01 Thread Slawa Olhovchenkov
On Sat, Dec 12, 2015 at 03:35:13PM +0200, Konstantin Belousov wrote: > On Sat, Dec 12, 2015 at 04:06:15PM +0300, Slawa Olhovchenkov wrote: > > Does STABLE support X2APIC? > > I see X2APIC related commits in CURRENT, what is status for STABLE? > > I am try to enable X2APIC

Re: X2APIC support

2016-09-01 Thread Slawa Olhovchenkov
On Thu, Sep 01, 2016 at 02:45:00PM +0300, Konstantin Belousov wrote: > On Thu, Sep 01, 2016 at 02:27:24PM +0300, Slawa Olhovchenkov wrote: > > On Sat, Dec 12, 2015 at 03:35:13PM +0200, Konstantin Belousov wrote: > > > > > On Sat, Dec 12, 2015 at 04:06:15PM +0300,

Re: X2APIC support

2016-09-01 Thread Slawa Olhovchenkov
On Thu, Sep 01, 2016 at 08:26:32PM +0300, Konstantin Belousov wrote: > On Thu, Sep 01, 2016 at 03:13:00PM +0300, Slawa Olhovchenkov wrote: > > On Thu, Sep 01, 2016 at 02:45:00PM +0300, Konstantin Belousov wrote: > > As I point before: 'X2APIC_OPT_OUT Flag'. > >

Re: X2APIC support

2016-09-01 Thread Slawa Olhovchenkov
On Thu, Sep 01, 2016 at 08:50:49PM +0300, Konstantin Belousov wrote: > On Thu, Sep 01, 2016 at 08:31:49PM +0300, Slawa Olhovchenkov wrote: > > On Thu, Sep 01, 2016 at 08:26:32PM +0300, Konstantin Belousov wrote: > > > > > On Thu, Sep 01, 2016 at 03:13:00PM +0300,

Re: X2APIC support

2016-09-01 Thread Slawa Olhovchenkov
On Thu, Sep 01, 2016 at 09:19:15PM +0300, Konstantin Belousov wrote: > On Thu, Sep 01, 2016 at 09:00:14PM +0300, Slawa Olhovchenkov wrote: > > Sorry, don't cleanly understund, what combination of BIOS setting I am need > > to probe? > > And what I am need to check? >

Re: X2APIC support

2016-09-01 Thread Slawa Olhovchenkov
On Thu, Sep 01, 2016 at 09:37:29PM +0200, sth...@nethelp.no wrote: > > > > Sorry, don't cleanly understund, what combination of BIOS setting I am > > > > need to probe? > > > > And what I am need to check? > > > > > > Set 'Hyper-Threading' to Enabled. > > > Set 'X2APIC_OPT_OUT' to Enabled. > > >

Re: 11.0-RELEASE status update

2016-09-01 Thread Slawa Olhovchenkov
On Thu, Sep 01, 2016 at 09:10:00PM +, Glen Barber wrote: > As some of you may be aware, a few last-minute showstoppers appeared > since 11.0-RC1 (and before RC1). > > One of the showstoppers has been fixed in 12-CURRENT, and merged to > stable/11 and releng/11.0 that affected booting from lar

Re: libmap32.conf on stable/11

2016-09-01 Thread Slawa Olhovchenkov
On Thu, Sep 01, 2016 at 02:24:11PM -0700, Bryan Drewery wrote: > On 9/1/2016 3:51 AM, Slawa Olhovchenkov wrote: > > libmap32.conf missing on 11.0-STABLE. > > It's no longer needed in the default install after r282420, it was > removed in r282421. > > > s

Re: X2APIC support

2016-09-04 Thread Slawa Olhovchenkov
On Sun, Sep 04, 2016 at 11:19:16AM +0300, Andriy Gapon wrote: > On 01/09/2016 15:13, Slawa Olhovchenkov wrote: > > DMAR: Found table at 0x79b32798 > > x2APIC available but disabled by DMAR table > > > Event timer "LAPIC" quality 600 > > LAPIC: ipi

11.0 messages regression

2016-09-04 Thread Slawa Olhovchenkov
After upgrading to 11.0 messages in message buffer to highly interlaced: da18: Fixed Direct Access SPC-4 SCSI device da18: Serial Number 162813454D9E da18: 600.000MB/s transfers da18: Command Queueing enabled da18: 500786MB (1025610768 512 byte sectors) mps3:0:1:0): UNMAPPED SMP: AP CPU #16 Launc

11.0 stuck on high network load

2016-09-04 Thread Slawa Olhovchenkov
I am try using 11.0 on Dual E5-2620 (no X2APIC). Under high network load and may be addtional conditional system go to unresponsible state -- no reaction to network and console (USB IPMI emulation). INVARIANTS give to high overhad. Is this exist some way to debug this? _

Re: 11.0 stuck on high network load

2016-09-05 Thread Slawa Olhovchenkov
On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > Under high network load and may be addtional conditional system go to > > unresponsible state -- no re

Re: 11.0 stuck on high network load

2016-09-05 Thread Slawa Olhovchenkov
On Mon, Sep 05, 2016 at 10:14:59AM -0600, Warner Losh wrote: > On Mon, Sep 5, 2016 at 1:43 AM, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > >> On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > >> > I a

Re: 11.0 stuck on high network load

2016-09-05 Thread Slawa Olhovchenkov
On Mon, Sep 05, 2016 at 11:50:28AM -0600, Warner Losh wrote: > > How to interoperable with USB stack (I am beware USB keyboard may be > > locked)? > > I've just done serial console, so I'm not sure. I think that it works... IPMI or hardware? > >> I've seen this at Netflix on one variant of our

Re: X2APIC support

2016-09-06 Thread Slawa Olhovchenkov
On Sun, Sep 04, 2016 at 11:19:16AM +0300, Andriy Gapon wrote: > On 01/09/2016 15:13, Slawa Olhovchenkov wrote: > > DMAR: Found table at 0x79b32798 > > x2APIC available but disabled by DMAR table > > > Event timer "LAPIC" quality 600 > > LAPIC: ipi

Re: X2APIC support

2016-09-06 Thread Slawa Olhovchenkov
On Tue, Sep 06, 2016 at 05:08:28PM +0300, Konstantin Belousov wrote: > On Tue, Sep 06, 2016 at 04:13:05PM +0300, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 11:19:16AM +0300, Andriy Gapon wrote: > > > > > On 01/09/2016 15:13, Slawa Olhovchenkov wrote: >

Re: 11.0 stuck on high network load

2016-09-06 Thread Slawa Olhovchenkov
On Mon, Sep 05, 2016 at 10:14:59AM -0600, Warner Losh wrote: > On Mon, Sep 5, 2016 at 1:43 AM, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > >> On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > >> > I a

nginx and FreeBSD11

2016-09-07 Thread Slawa Olhovchenkov
I am have strange issuse with nginx on FreeBSD11. I am have FreeBSD11 instaled over STABLE-10. nginx build for FreeBSD10 and run w/o recompile work fine. nginx build for FreeBSD11 crushed inside rbtree lookups: next node totaly craped. I am see next potential cause: 1) clang 3.8 code generation i

Re: nginx and FreeBSD11

2016-09-07 Thread Slawa Olhovchenkov
On Wed, Sep 07, 2016 at 08:29:04PM +0100, Matt Smith wrote: > On Sep 07 22:13, Slawa Olhovchenkov wrote: > >I am have strange issuse with nginx on FreeBSD11. > >I am have FreeBSD11 instaled over STABLE-10. > >nginx build for FreeBSD10 and run w/o recompile work fine.

Re: X2APIC support

2016-09-12 Thread Slawa Olhovchenkov
On Sun, Sep 04, 2016 at 08:14:07PM +0300, Andriy Gapon wrote: > On 04/09/2016 19:29, Konstantin Belousov wrote: > > This is possible, of course. But it would not affect "SMP: Added CPU ..." > > lines. > > Well, looking at the code it seems that only if mptable is used, then those > lines are exp

Re: X2APIC support

2016-09-12 Thread Slawa Olhovchenkov
On Mon, Sep 12, 2016 at 04:44:09PM +0300, Andriy Gapon wrote: > On 12/09/2016 12:39, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 08:14:07PM +0300, Andriy Gapon wrote: > > > >> On 04/09/2016 19:29, Konstantin Belousov wrote: > >>> This is possible,

Re: X2APIC support

2016-09-12 Thread Slawa Olhovchenkov
On Mon, Sep 12, 2016 at 08:05:33PM +0300, Andriy Gapon wrote: > On 12/09/2016 19:44, Slawa Olhovchenkov wrote: > > I am not kernel developer: please point what I am need insert and file > > for edit. > > In sys/amd64/amd64/mp_machdep.c (assuming you use amd64), in functi

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov
On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote: > On 12/09/2016 20:53, Slawa Olhovchenkov wrote: > > boot_cpu_id = 255 > > I think that this points towards the BIOS not configuring the BSP LAPIC > correctly when you select that combination of BIOS options. >

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov
On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote: > On 13/09/2016 15:11, Slawa Olhovchenkov wrote: > > On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote: > > > >> On 12/09/2016 20:53, Slawa Olhovchenkov wrote: > >>> boot_cpu_id = 25

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov
On Tue, Sep 13, 2016 at 03:57:39PM +0300, Andriy Gapon wrote: > On 13/09/2016 15:42, Slawa Olhovchenkov wrote: > > On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote: > > > >> On 13/09/2016 15:11, Slawa Olhovchenkov wrote: > >>> On Tue, Sep 13, 20

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov
On Tue, Sep 13, 2016 at 05:54:26PM +0300, Andriy Gapon wrote: > On 13/09/2016 17:21, Slawa Olhovchenkov wrote: > > boot failed: > > > > set hw.x2apic_enable=0 > > loading required module 'krpc' > > /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e0

Re: X2APIC support

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 02:36:34PM +0300, Konstantin Belousov wrote: > On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: > > On 13/09/2016 18:22, Konstantin Belousov wrote: > > > Any access > > > to the LAPIC registers page in x2APIC mode faults. > > > > Is this a fact? > > I read the

Re: X2APIC support

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 03:22:17PM +0300, Andriy Gapon wrote: > On 14/09/2016 14:36, Konstantin Belousov wrote: > > On Tue, Sep 13, 2016 at 06:52:19PM +0300, Andriy Gapon wrote: > >> On 13/09/2016 18:22, Konstantin Belousov wrote: > >>> Any access > >>> to the LAPIC registers page in x2APIC mode f

Re: X2APIC support

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 03:35:39PM +0300, Andriy Gapon wrote: > On 14/09/2016 15:33, Slawa Olhovchenkov wrote: > > On Wed, Sep 14, 2016 at 03:22:17PM +0300, Andriy Gapon wrote: > > > >> On 14/09/2016 14:36, Konstantin Belousov wrote: > >>> On Tue, Sep 13, 20

Re: X2APIC support

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 07:08:02PM +0300, Konstantin Belousov wrote: > On Wed, Sep 14, 2016 at 05:02:21PM +0300, Andriy Gapon wrote: > > On 14/09/2016 15:49, Slawa Olhovchenkov wrote: > > > MSR_APICBASE = 0xfee00d00 > > > x2APIC is prohibited but turned

Re: 11.0 stuck on high network load

2016-09-14 Thread Slawa Olhovchenkov
On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > Under high network load and may be addtional conditional system go to > > unresponsible state -- no re

Re: 11.0 stuck on high network load

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > I a

Re: 11.0 stuck on high network load

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 02:56:57PM -0700, hiren panchasara wrote: > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: > > > > I a

Re: 11.0 stuck on high network load

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 03:04:20PM -0700, hiren panchasara wrote: > On 09/15/16 at 12:57P, Slawa Olhovchenkov wrote: > > On Wed, Sep 14, 2016 at 02:43:06PM -0700, hiren panchasara wrote: > > > > > On 09/15/16 at 12:35P, Slawa Olhovchenkov wrote: > > > > On S

Re: 11.0 stuck on high network load

2016-09-14 Thread Slawa Olhovchenkov
On Wed, Sep 14, 2016 at 11:23:20PM +0100, Gary Palmer wrote: > On Thu, Sep 15, 2016 at 01:13:35AM +0300, Slawa Olhovchenkov wrote: > > On Wed, Sep 14, 2016 at 03:04:20PM -0700, hiren panchasara wrote: > > > > > On 09/15/16 at 12:57P, Slawa Olhovchenkov wrote: > >

Re: 11.0 stuck on high network load

2016-09-14 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 02:33:07AM +0300, Oleksandr V. Typlyns'kyi wrote: > Sep 5 Sep 5, 2016 at 00:57 Slawa Olhovchenkov wrote: > > > I am try using 11.0 on Dual E5-2620 (no X2APIC). > > Under high network load and may be addtional conditional system go to > > unres

Re: 11.0 stuck on high network load

2016-09-15 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > On 09/05/16 at 12:57P, Slawa Olhovchenkov wrote: >

Re: nginx and FreeBSD11

2016-09-15 Thread Slawa Olhovchenkov
On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > I am have strange issuse with nginx on FreeBSD11. > I am have FreeBSD11 instaled over STABLE-10. > nginx build for FreeBSD10 and run w/o recompile work fine. > nginx build for FreeBSD11 crushed inside rbtree lookup

Re: nginx and FreeBSD11

2016-09-15 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 09:52:30AM -0700, jungle Boogie wrote: > On 15 September 2016 at 07:41, Slawa Olhovchenkov wrote: > > Bingo! > > aio read file by process 1055 placed to same memory address as requested > > but in memory space of process 1060! > > > > Thi

Re: nginx and FreeBSD11

2016-09-15 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > > On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > > > > > I am have strange issuse with nginx on FreeBSD11. &

Re: nginx and FreeBSD11

2016-09-15 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote: > > > Index: vfs_aio.c > > > === > > > --- vfs_aio.c (revision 305811) > > > +++ vfs_aio.c (working copy) > > > @@ -787,6 +787,8 @@ aio_process_rw(struct kaiocb *jo

Re: nginx and FreeBSD11

2016-09-15 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote: > On Thursday, September 15, 2016 08:49:48 PM Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > > > > > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenk

Re: nginx and FreeBSD11

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 12:16:17PM +0300, Konstantin Belousov wrote: > > vmspace_switch_aio() allows context switching with old curpmap > and new proc->p_vmspace. This is a weird condition, where > curproc->p_vmspace->vm_pmap is not equal to curcpu->pc_curpmap. I do > not see an obvious place whi

Re: nginx and FreeBSD11

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 01:17:14PM +0300, Slawa Olhovchenkov wrote: > On Fri, Sep 16, 2016 at 12:16:17PM +0300, Konstantin Belousov wrote: > > > > > vmspace_switch_aio() allows context switching with old curpmap > > and new proc->p_vmspace. This is a weird c

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, h

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: &g

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: &g

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve > performance for short-lived connections. I am not too sure if thats the > problem

Re: 11.0 stuck on high network load

2016-09-17 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 02:48:49PM -0700, hiren panchasara wrote: > On 09/16/16 at 02:46P, hiren panchasara wrote: > > On 09/16/16 at 11:30P, Slawa Olhovchenkov wrote: > > > On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > > > > > > > &g

Re: nginx and FreeBSD11

2016-09-18 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > > On Wed, Sep 07, 2016 at 10:13:48PM +0300, Slawa Olhovchenkov wrote: > > > > > I am have strange issuse with nginx on FreeBSD11. &

Re: 11.0 stuck on high network load

2016-09-18 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > + jch@ > On 09/16/16 at 10:03P, Slawa Olhovchenkov wrote: > > On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > > > > > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > >

Re: 11.0 stuck on high network load

2016-09-18 Thread Slawa Olhovchenkov
On Sun, Sep 18, 2016 at 07:50:08PM +0200, Hans Petter Selasky wrote: > Hi, > > Got some tips regarding this thread. > > Some things you can try: > > 1) Compile kernel from projects/hps_head instead of your 11-stable? How many difference from 11-stable? > 2) Set net.inet.tcp.per_cpu_timers=1

Re: 11.0 stuck on high network load

2016-09-18 Thread Slawa Olhovchenkov
On Sun, Sep 18, 2016 at 10:38:58PM +0200, Hans Petter Selasky wrote: > On 09/18/16 20:10, Slawa Olhovchenkov wrote: > > On Sun, Sep 18, 2016 at 07:50:08PM +0200, Hans Petter Selasky wrote: > > > >> Hi, > >> > >> Got some tips regarding this thread. >

Re: 11.0 stuck on high network load

2016-09-19 Thread Slawa Olhovchenkov
On Mon, Sep 19, 2016 at 10:32:13PM +0200, Julien Charbon wrote: > > > @ CPU_CLK_UNHALTED_CORE [4653445 samples] > > > > 51.86% [2413083] lock_delay @ /boot/kernel.VSTREAM/kernel > > 100.0% [2413083] __rw_wlock_hard > > 100.0% [2413083]tcp_tw_2msl_scan > >99.99% [2412958] pf

Re: LAGG and Jumbo Frames

2016-09-19 Thread Slawa Olhovchenkov
On Mon, Sep 19, 2016 at 02:28:56PM -0700, Lyndon Nerenberg wrote: > > Everything on physical Ethernet has support for it Including the LAN > > interface of Firewall, and talks to it just fine over a single interface > > with > > Jumbo frames enabled. > > Well, before you get too carried away,

Re: nginx and FreeBSD11

2016-09-19 Thread Slawa Olhovchenkov
On Mon, Sep 19, 2016 at 06:05:46PM -0700, John Baldwin wrote: > > > If this panics, then vmspace_switch_aio() is not working for > > > some reason. > > > > I am try using next DTrace script: > > > > #pragma D option dynvarsize=64m > > > > int req[struct vmspace *, void *]; > > self int tra

Re: LAGG and Jumbo Frames

2016-09-20 Thread Slawa Olhovchenkov
On Mon, Sep 19, 2016 at 03:59:20PM -0700, Lyndon Nerenberg wrote: > > > On Sep 19, 2016, at 3:08 PM, Slawa Olhovchenkov wrote: > > > > This is because RTT of this link for jumbo frames higher 1500 bytes > > frame for store-and-forward switch chain. > > For T

Re: nginx and FreeBSD11

2016-09-20 Thread Slawa Olhovchenkov
On Tue, Sep 20, 2016 at 09:52:44AM +0300, Slawa Olhovchenkov wrote: > On Mon, Sep 19, 2016 at 06:05:46PM -0700, John Baldwin wrote: > > > > > If this panics, then vmspace_switch_aio() is not working for > > > > some reason. > > > > > > I am try us

Re: 11.0 stuck on high network load

2016-09-20 Thread Slawa Olhovchenkov
On Tue, Sep 20, 2016 at 10:00:25PM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 9/19/16 10:43 PM, Slawa Olhovchenkov wrote: > > On Mon, Sep 19, 2016 at 10:32:13PM +0200, Julien Charbon wrote: > >> > >>> @ CPU_CLK_UNHALTED_CORE [4653445 samples] &g

Re: nginx and FreeBSD11

2016-09-20 Thread Slawa Olhovchenkov
On Tue, Sep 20, 2016 at 11:19:25PM +0300, Konstantin Belousov wrote: > On Tue, Sep 20, 2016 at 10:20:53PM +0300, Slawa Olhovchenkov wrote: > > On Tue, Sep 20, 2016 at 09:52:44AM +0300, Slawa Olhovchenkov wrote: > > > > > On Mon, Sep 19, 2016 at 06:05:46PM -

Re: nginx and FreeBSD11

2016-09-20 Thread Slawa Olhovchenkov
On Wed, Sep 21, 2016 at 12:15:17AM +0300, Konstantin Belousov wrote: > On Tue, Sep 20, 2016 at 11:38:54PM +0300, Slawa Olhovchenkov wrote: > > On Tue, Sep 20, 2016 at 11:19:25PM +0300, Konstantin Belousov wrote: > > > > > On Tue, Sep 20, 2016 at 10:20:53PM +0300,

Re: nginx and FreeBSD11

2016-09-20 Thread Slawa Olhovchenkov
On Tue, Sep 20, 2016 at 04:00:10PM -0600, Warner Losh wrote: > >> > > Is this sandy bridge ? > >> > > >> > Sandy Bridge EP > >> > > >> > > Show me first 100 lines of the verbose dmesg, > >> > > >> > After day or two, after end of this test run -- I am need to enable > >> > verbose. > >> > > >> >

Re: 11.0 stuck on high network load

2016-09-21 Thread Slawa Olhovchenkov
On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 9/20/16 10:26 PM, Slawa Olhovchenkov wrote: > > On Tue, Sep 20, 2016 at 10:00:25PM +0200, Julien Charbon wrote: > >> On 9/19/16 10:43 PM, Slawa Olhovchenkov wrote: > >>

Re: 11.0 stuck on high network load

2016-09-21 Thread Slawa Olhovchenkov
On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote: > > You can also use Dtrace and lockstat (especially with the lockstat -s > option): > > https://wiki.freebsd.org/DTrace/One-Liners#Kernel_Locks > https://www.freebsd.org/cgi/man.cgi?query=lockstat&manpath=FreeBSD+11.0-RELEASE > >

Re: nginx and FreeBSD11

2016-09-22 Thread Slawa Olhovchenkov
On Thu, Sep 22, 2016 at 10:59:33AM +0300, Konstantin Belousov wrote: > On Wed, Sep 21, 2016 at 12:15:17AM +0300, Konstantin Belousov wrote: > > > > diff --git a/sys/vm/vm_map.c b/sys/vm/vm_map.c > > > > index a23468e..f754652 100644 > > > > --- a/sys/vm/vm_map.c > > > > +++ b/sys/vm/vm_map.c > > >

Re: nginx and FreeBSD11

2016-09-22 Thread Slawa Olhovchenkov
On Thu, Sep 22, 2016 at 11:27:40AM +0300, Konstantin Belousov wrote: > On Thu, Sep 22, 2016 at 11:25:27AM +0300, Slawa Olhovchenkov wrote: > > On Thu, Sep 22, 2016 at 10:59:33AM +0300, Konstantin Belousov wrote: > > > Below is, I believe, the committable fix, of course suppos

Re: nginx and FreeBSD11

2016-09-22 Thread Slawa Olhovchenkov
On Thu, Sep 22, 2016 at 11:53:20AM +0300, Konstantin Belousov wrote: > On Thu, Sep 22, 2016 at 11:34:24AM +0300, Slawa Olhovchenkov wrote: > > On Thu, Sep 22, 2016 at 11:27:40AM +0300, Konstantin Belousov wrote: > > > > > On Thu, Sep 22, 2016 at 11:25:27AM +0300,

Re: 11.0 stuck on high network load

2016-09-22 Thread Slawa Olhovchenkov
On Thu, Sep 22, 2016 at 11:28:38AM +0200, Julien Charbon wrote: > >>> What purpose to not skip locked tcptw in this loop? > >> > >> If I understand your question correctly: According to your pmcstat > >> result, tcp_tw_2msl_scan() currently struggles with a write lock > >> (__rw_wlock_hard) and

Re: 11.0 stuck on high network load

2016-09-22 Thread Slawa Olhovchenkov
On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote: > > On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote: > >> You can also use Dtrace and lockstat (especially with

Re: 11.0 stuck on high network load

2016-09-22 Thread Slawa Olhovchenkov
On Thu, Sep 22, 2016 at 12:04:40PM +0200, Julien Charbon wrote: > >> These paths can indeed compete for the same INP lock, as both > >> tcp_tw_2msl_scan() calls always start with the first inp found in > >> twq_2msl list. But in both cases, this first inp should be quickly used > >> and its lock

Re: zvol clone diffs

2016-09-22 Thread Slawa Olhovchenkov
On Thu, Sep 22, 2016 at 04:56:53PM +0500, Eugene M. Zheganin wrote: > Hi. > > I should mention from the start that this is a question about an > engineering task, not a question about FreeBSD issue. > > I have a set of zvol clones that I redistribute over iSCSI. Several > Windows VMs use these c

Re: 11.0 stuck on high network load

2016-09-23 Thread Slawa Olhovchenkov
On Thu, Sep 22, 2016 at 01:20:45PM +0300, Slawa Olhovchenkov wrote: > On Thu, Sep 22, 2016 at 12:04:40PM +0200, Julien Charbon wrote: > > > >> These paths can indeed compete for the same INP lock, as both > > >> tcp_tw_2msl_scan() calls always start with the firs

Re: 11.0 stuck on high network load

2016-09-23 Thread Slawa Olhovchenkov
On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote: > > On Wed, Sep 21, 2016 at 09:11:24AM +0200, Julien Charbon wrote: > >> You can also use Dtrace and lockstat (especially with

Re: 11.0 stuck on high network load

2016-09-25 Thread Slawa Olhovchenkov
On Fri, Sep 23, 2016 at 11:01:43PM +0300, Slawa Olhovchenkov wrote: > On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrote: > > > > > Hi Slawa, > > > > On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote: > > > On Wed, Sep 21, 2016 at 09:11:24AM +0200

Re: 11.0 stuck on high network load

2016-09-25 Thread Slawa Olhovchenkov
On Fri, Sep 23, 2016 at 10:16:56PM +0300, Slawa Olhovchenkov wrote: > On Thu, Sep 22, 2016 at 01:20:45PM +0300, Slawa Olhovchenkov wrote: > > > On Thu, Sep 22, 2016 at 12:04:40PM +0200, Julien Charbon wrote: > > > > > >> These paths can indeed compe

Re: 11.0 stuck on high network load

2016-09-26 Thread Slawa Olhovchenkov
On Mon, Sep 26, 2016 at 10:51:07AM +0200, Julien Charbon wrote: > > 1049 kqread- I 145:58.35 nginx: worker process (nginx) > > 1050 kqread- I 136:33.36 nginx: worker process (nginx) > > 1051 kqread- I 140:59.73 nginx: worker process (nginx) > > 1052 kqread- I

Re: 11.0 stuck on high network load

2016-09-26 Thread Slawa Olhovchenkov
On Mon, Sep 26, 2016 at 11:33:12AM +0200, Julien Charbon wrote: > >>> - tcp_input()/tcp_twstart()/tcp_tw_2msl_scan(reuse=1) > >> > >> My current hypothesis: > >> > >> nginx do write() (or may be close()?) to socket, kernel lock > >> first inp in V_twq_2msl, happen callout for pfslowtimo() on the

Re: 11.0 stuck on high network load

2016-09-26 Thread Slawa Olhovchenkov
On Mon, Sep 26, 2016 at 01:57:03PM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 9/25/16 2:46 PM, Slawa Olhovchenkov wrote: > > On Fri, Sep 23, 2016 at 11:01:43PM +0300, Slawa Olhovchenkov wrote: > >> On Wed, Sep 21, 2016 at 11:25:18PM +0200, Julien Charbon wrot

Re: nginx and FreeBSD11

2016-09-26 Thread Slawa Olhovchenkov
On Mon, Sep 26, 2016 at 06:20:42PM +0300, Konstantin Belousov wrote: > On Thu, Sep 22, 2016 at 12:33:55PM +0300, Slawa Olhovchenkov wrote: > > OK, try this patch. > > Was the patch tested ? No more AIO related issused/nginx core dumps. I Can't get long uptime by other is

Re: 11.0 stuck on high network load

2016-09-26 Thread Slawa Olhovchenkov
On Mon, Sep 26, 2016 at 11:33:12AM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 9/25/16 2:46 PM, Slawa Olhovchenkov wrote: > > On Fri, Sep 23, 2016 at 11:01:43PM +0300, Slawa Olhovchenkov wrote: > >>> On 9/21/16 9:51 PM, Slawa Olhovchenkov wrote: > >&g

Re: 11.0 stuck on high network load

2016-09-28 Thread Slawa Olhovchenkov
On Wed, Sep 28, 2016 at 12:06:47PM +0200, Julien Charbon wrote: > > Tracing command intr pid 12 tid 100026 td 0xf8011424b500 > > sched_switch() at 0x804c956d = sched_switch+0x6ad/frame > > 0xfe3876f0 > > mi_switch() at 0x804a8d92 = mi_switch+0xd2/frame 0xfe3877

Re: 11.0 stuck on high network load

2016-10-06 Thread Slawa Olhovchenkov
On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > 2. thread1: In tcp_close() the inp is marked with INP_DROPPED flag, the > process continues and calls INP_WUNLOCK() here: > > https://github.com/freebsd/freebsd/blob/releng/11.0/sys/netinet/tcp_subr.c#L1568 Look also to sys/netin

Re: 11.0 stuck on high network load

2016-10-07 Thread Slawa Olhovchenkov
On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > Thanks again to Slawa, for his numerous debug reports and always > questioning my explanations. His last question directly led to this > finding. He is testing a quick workaround patch to check if there is more. Thanks very matc

11.0-RELEASE and mbuf-related trace

2016-10-07 Thread Slawa Olhovchenkov
Has anybody comment on this? During debug tcp-related freeze I am collect starnge mbuf-related freeze (this is like recursive lock to UMA Slabs keg) and trace: last pid: 49575; load averages: 2.00, 2.05, 3.75up 1+01:12:08 22:13:42 853 processes: 15 running, 769 sleeping, 35 waiting, 34 lo

Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: > > Hi, > > On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > > On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > > > >> 2. thread1: In tcp_close() the inp is marked with I

Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: > > Hi, > > On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > > On Thu, Oct 06, 2016 at 09:28:06AM +0200, Julien Charbon wrote: > > > >> 2. thread1: In tcp_close() the inp is marked with I

Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 04:03:39PM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 10/10/16 3:32 PM, Slawa Olhovchenkov wrote: > > On Mon, Oct 10, 2016 at 01:26:12PM +0200, Julien Charbon wrote: > >> On 10/6/16 1:10 PM, Slawa Olhovchenkov wrote: > >>> O

Re: 11.0 stuck on high network load

2016-10-10 Thread Slawa Olhovchenkov
On Mon, Oct 10, 2016 at 05:44:21PM +0200, Julien Charbon wrote: > >> can check the current other usages of goto findpcb in tcp_input(). The > >> rational here being: > >> > >> - Behavior before the patch: If the inp we found was deleted then goto > >> findpcb. > >> - Behavior after the patch:

Re: 11.0 stuck on high network load

2016-10-11 Thread Slawa Olhovchenkov
On Tue, Oct 11, 2016 at 09:20:17AM +0200, Julien Charbon wrote: > Then threads are competing for the INP_WLOCK lock. For the example, > let's say the thread A wants to run tcp_input()/in_pcblookup_mbuf() and > racing for this INP_WLOCK: > > https://github.com/freebsd/freebsd/blob/release/11.0.0

Re: 11.0 stuck on high network load

2016-10-12 Thread Slawa Olhovchenkov
On Wed, Oct 12, 2016 at 10:18:18AM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 10/11/16 2:11 PM, Slawa Olhovchenkov wrote: > > On Tue, Oct 11, 2016 at 09:20:17AM +0200, Julien Charbon wrote: > >> Then threads are competing for the INP_WLOCK lock. For the

Re: 11.0 stuck on high network load

2016-10-12 Thread Slawa Olhovchenkov
On Wed, Oct 12, 2016 at 11:19:48AM +0200, Julien Charbon wrote: > > if INP_WLOCK is like spinlock -- this is dead lock. > > if INP_WLOCK is like mutex -- thread1 resheduled. > > Thanks, I understand you question now. No an interrupt cannot bypass a > lock: Here INP_WLOCK is like mutex -- threa

Re: 11.0 stuck on high network load

2016-10-12 Thread Slawa Olhovchenkov
On Wed, Oct 12, 2016 at 11:42:38AM +0200, Julien Charbon wrote: > On 10/12/16 11:29 AM, Slawa Olhovchenkov wrote: > > On Wed, Oct 12, 2016 at 11:19:48AM +0200, Julien Charbon wrote: > > > >>> if INP_WLOCK is like spinlock -- this is dead lock. > >>>

Re: 11.0 stuck on high network load

2016-10-12 Thread Slawa Olhovchenkov
On Wed, Oct 12, 2016 at 02:06:59PM +0200, Julien Charbon wrote: > > sofree() call tcp_usr_detach() and in tcp_usr_detach() we have > > unexpected INP_TIMEWAIT. > > I see, thus just for the context: The TCP stack in sys/dev/cxgb* is a > TOE (TCP Offload Engine?) TCP stack f

Re: 11.0 stuck on high network load

2016-10-12 Thread Slawa Olhovchenkov
On Wed, Oct 12, 2016 at 02:35:11PM +0200, Julien Charbon wrote: > > Hi Slawa, > > On 10/12/16 2:13 PM, Slawa Olhovchenkov wrote: > > On Wed, Oct 12, 2016 at 02:06:59PM +0200, Julien Charbon wrote: > >>>>>>> sofree() call tcp_usr_detach() and in tcp

Re: 11.0 stuck on high network load

2016-10-12 Thread Slawa Olhovchenkov
On Wed, Oct 12, 2016 at 05:17:35PM +0200, Julien Charbon wrote: > I see, thus just for the context: The TCP stack in sys/dev/cxgb* > is a > TOE (TCP Offload Engine?) TCP stack for Chelsio NICs, it is a > separate/side TCP stack that is used only with TCP_OFFL

Re: 11.0 stuck on high network load

2016-10-13 Thread Slawa Olhovchenkov
On Thu, Oct 13, 2016 at 01:56:21PM +0200, Julien Charbon wrote: > >> Something like: > > > > Yes, thanks! > > Proposed changes added in the review: > > https://reviews.freebsd.org/D8211 > > tell me when you have three days without issue with this change. > > >> tcp_detach() { > >> > >> .

Re: 11.0 stuck on high network load

2016-10-13 Thread Slawa Olhovchenkov
On Thu, Oct 13, 2016 at 05:06:00PM +0200, Julien Charbon wrote: > >> will give you that trace in the core, and without INVARIANT then it is > >> better to use dtrace: > >> > >> $ cat tcp-twstart-dropped.d > >> fbt::tcp_twstart:entry > >> /args[0]->t_inpcb->inp_flags & 0x0400/ > >> { > >> sta

Re: 11.0 stuck on high network load

2016-10-14 Thread Slawa Olhovchenkov
On Thu, Oct 13, 2016 at 06:14:29PM +0200, Julien Charbon wrote: > On 10/13/16 5:17 PM, Slawa Olhovchenkov wrote: > > On Thu, Oct 13, 2016 at 05:06:00PM +0200, Julien Charbon wrote: > > > >>>> will give you that trace in the core, and without INVARIANT then it

Re: 11.0 stuck on high network load

2016-10-14 Thread Slawa Olhovchenkov
On Fri, Oct 14, 2016 at 11:48:38AM +0200, Julien Charbon wrote: > >>> Also, using dtrace too complex in production (need complex startup > >>> under screen and capture output) and for many peoples. > >>> kdb_backtrace() have too less administrative overhead. > >> > >> I still think it is overkill

<    1   2   3   4   >