Re: r309145: mutex.h:369:5: error: 'LOCK_DEBUG' is not defined

2016-11-25 Thread O. Hartmann
Am Fri, 25 Nov 2016 08:40:51 -0800 David Wolfskill schrieb: > On Fri, Nov 25, 2016 at 05:34:51PM +0100, O. Hartmann wrote: > > Recent sources do not build kernel due to: > > > > [...] > > Building /usr/obj/usr/src/sys/SB21X1/ipsec_mbuf.o > > In file included from

Re: NFSv4 performance degradation with 12.0-CURRENT client

2016-11-25 Thread Alan Somers
On Fri, Nov 25, 2016 at 6:57 AM, Konstantin Belousov wrote: > On Fri, Nov 25, 2016 at 12:54:07PM +, Rick Macklem wrote: >> Well, ideally theer would be a VOP_MMAPDONE() or something like that, which >> would tell the NFSv4 client that I/O is done on the vnode so it can

Please test EARLY_AP_STARTUP

2016-11-25 Thread John Baldwin
I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks have been testing it for the last week or so which has exposed some additional things to fix. I think I've resolved most of those in one way or another, but it will make things smoother if other folks can start testing this

r309145: mutex.h:369:5: error: 'LOCK_DEBUG' is not defined

2016-11-25 Thread O. Hartmann
Recent sources do not build kernel due to: [...] Building /usr/obj/usr/src/sys/SB21X1/ipsec_mbuf.o In file included from /usr/src/sys/netipsec/ipsec_mbuf.c:43: In file included from /usr/src/sys/netipsec/ipsec.h:46: In file included from /usr/src/sys/netipsec/keydb.h:38:

Re: NFSv4 performance degradation with 12.0-CURRENT client

2016-11-25 Thread Rick Macklem
Konstantin Belousov wrote: >On Thu, Nov 24, 2016 at 10:45:51PM +, Rick Macklem wrote: >> asom...@gmail.com wrote: >> >OpenOwner Opens LockOwner LocksDelegs LocalOwn LocalOpen >> >LocalLOwn >> > 5638141453 0 0 0 0 0 >> > 0

Re: NFSv4 performance degradation with 12.0-CURRENT client

2016-11-25 Thread O. Hartmann
Am Thu, 24 Nov 2016 22:35:42 +0200 Konstantin Belousov schrieb: > On Thu, Nov 24, 2016 at 11:42:41AM -0700, Alan Somers wrote: > > On Thu, Nov 24, 2016 at 5:53 AM, Rick Macklem wrote: > > > > > > > > On Wed, Nov 23, 2016 at 10:17:25PM -0700, Alan

Re: NFSv4 performance degradation with 12.0-CURRENT client

2016-11-25 Thread Konstantin Belousov
On Fri, Nov 25, 2016 at 12:54:07PM +, Rick Macklem wrote: > Well, ideally theer would be a VOP_MMAPDONE() or something like that, which > would tell the NFSv4 client that I/O is done on the vnode so it can close it. > If there was some way for the NFSv4 VOP_CLOSE() to be able to tell if the

Re: NFSv4 performance degradation with 12.0-CURRENT client

2016-11-25 Thread Konstantin Belousov
On Thu, Nov 24, 2016 at 10:45:51PM +, Rick Macklem wrote: > asom...@gmail.com wrote: > >OpenOwner Opens LockOwner LocksDelegs LocalOwn LocalOpen > >LocalLOwn > > 5638141453 0 0 0 0 0 > > 0 > Ok, I think this shows us the