On Sat, Nov 26, 2016 at 11:19:19PM +, Rick Macklem wrote:
> Konstantin Belousov wrote:
> [stuff snipped]
> >I thought that the issue was in tracking any opens and mmaps, but from this
> >reply it is not that clear. Do you need callback when all opens and mmaps
> >have ended, or only opens and
Alan Somers wrote:
[stuff snipped]
>Mounting nullfs with the nocache option, ad kib suggested, fixed the
>problem. Also, applying kib's patch and then mounting nullfs with
>default options also fixed the problem. Here is the nfsstat output
>for "ls -al" when using kib's patch. Notice the client
Konstantin Belousov wrote:
[stuff snipped]
>I thought that the issue was in tracking any opens and mmaps, but from this
>reply it is not that clear. Do you need callback when all opens and mmaps
>have ended, or only opens and mmaps for write ? If later, we already have
>a suitable mechanism VOP_A
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 close it.
>> If there wa
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
>
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 Somers wrote:
> > >> I have a FreeBSD 10.3-R
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 fil
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 pro
asom...@gmail.com wrote:
[stuff snipped]
>I've reproduced the issue on stock FreeBSD 12, and I've also learned
>that nullfs is a required factor. Doing the buildworld directly on
>the NFS mount doesn't cause any slowdown, but doing a buildworld on
>the nullfs copy of the NFS mount does. The slowd
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 Somers wrote:
> >> I have a FreeBSD 10.3-RELEASE-p12 server exporting its home
> >> directories over both NFSv3 and NFSv4. I h
On Thu, Nov 24, 2016 at 5:53 AM, Rick Macklem wrote:
>
> On Wed, Nov 23, 2016 at 10:17:25PM -0700, Alan Somers wrote:
>> I have a FreeBSD 10.3-RELEASE-p12 server exporting its home
>> directories over both NFSv3 and NFSv4. I have a TrueOS client (based
>> on 12.0-CURRENT on the drm-next-4.7 branc
On Wed, Nov 23, 2016 at 10:17:25PM -0700, Alan Somers wrote:
> I have a FreeBSD 10.3-RELEASE-p12 server exporting its home
> directories over both NFSv3 and NFSv4. I have a TrueOS client (based
> on 12.0-CURRENT on the drm-next-4.7 branch, built on 28-October)
> mounting the home directories over
On Wed, Nov 23, 2016 at 10:17:25PM -0700, Alan Somers wrote:
> I have a FreeBSD 10.3-RELEASE-p12 server exporting its home
> directories over both NFSv3 and NFSv4. I have a TrueOS client (based
> on 12.0-CURRENT on the drm-next-4.7 branch, built on 28-October)
> mounting the home directories over
I have a FreeBSD 10.3-RELEASE-p12 server exporting its home
directories over both NFSv3 and NFSv4. I have a TrueOS client (based
on 12.0-CURRENT on the drm-next-4.7 branch, built on 28-October)
mounting the home directories over NFSv4. At first, everything is
fine and performance is good. But if
14 matches
Mail list logo
