Re: [Nfs-ganesha-devel] A question about rpc requests maybe for Bill

2018-03-15 Thread Frank Filz
> On 3/15/18 7:57 PM, Frank Filz wrote: > > NFS v4.1 has a max request size option for the session, I’m wondering if > there’s a way to get the size of a given request easily. > > > Depends on how that's defined. Bytes following header? And what you need to > do with it. > > It might be

Re: [Nfs-ganesha-devel] A question about rpc requests maybe for Bill

2018-03-15 Thread William Allen Simpson
On 3/15/18 7:57 PM, Frank Filz wrote: NFS v4.1 has a max request size option for the session, I’m wondering if there’s a way to get the size of a given request easily. Depends on how that's defined. Bytes following header? And what you need to do with it. It might be simplest to add a data

[Nfs-ganesha-devel] DSESS9002 and DSESS9003 test cases result in NFS4ERR_GRACE

2018-03-15 Thread Frank Filz
Does anyone know why an open well after Ganesha comes up is returning NFS4ERR_GRACE? I think it has something to do with the cid_reclaim_complete in the NFS v4.1 clientid. Thanks Frank -- Check out the vibrant

[Nfs-ganesha-devel] A question about rpc requests maybe for Bill

2018-03-15 Thread Frank Filz
NFS v4.1 has a max request size option for the session, I'm wondering if there's a way to get the size of a given request easily. Thanks Frank -- Check out the vibrant tech community on one of the world's most

Re: [Nfs-ganesha-devel] rpcping

2018-03-15 Thread Daniel Gryniewicz
100k is a much more accurate measurement. I haven't gotten any crashes since the fixes from yesterday, but I can keep trying. On Thu, Mar 15, 2018 at 12:10 PM, William Allen Simpson wrote: > On 3/15/18 10:23 AM, Daniel Gryniewicz wrote: >> >> Can you try again

Re: [Nfs-ganesha-devel] rpcping

2018-03-15 Thread William Allen Simpson
On 3/15/18 10:23 AM, Daniel Gryniewicz wrote: Can you try again with a larger count, like 100k? 500 is still quite small for a loop benchmark like this. In the code, I commented that 500 is minimal. I've done a pile of 100, 200, 300, and they perform roughly the same as 500. rpcping tcp

Re: [Nfs-ganesha-devel] rpcping

2018-03-15 Thread Daniel Gryniewicz
Can you try again with a larger count, like 100k? 500 is still quite small for a loop benchmark like this. Daniel On Thu, Mar 15, 2018 at 9:02 AM, William Allen Simpson wrote: > On 3/14/18 3:33 AM, William Allen Simpson wrote: >> >> rpcping tcp localhost

Re: [Nfs-ganesha-devel] rpcping

2018-03-15 Thread William Allen Simpson
On 3/14/18 3:33 AM, William Allen Simpson wrote: rpcping tcp localhost threads=1 count=500 (port=2049 program=13 version=3 procedure=0): mean 51285.7754, total 51285.7754 DanG pushed the latest code onto ntirpc this morning, and I'll submit a pullup for Ganesha later today. I've changed

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: cmake/efence: fix USE_EFENCE

2018-03-15 Thread GerritHub
>From Dominique Martinet : Dominique Martinet has uploaded this change for review. ( https://review.gerrithub.io/403963 Change subject: cmake/efence: fix USE_EFENCE .. cmake/efence: fix USE_EFENCE

Re: [Nfs-ganesha-devel] intermittent malloc list corruption on shutdown in -dev.3

2018-03-15 Thread Dominique Martinet
Hi all, I tracked this crash down and submitted a couple of patches here: https://github.com/nfs-ganesha/ntirpc/pull/120 These are NOT good as they are: I'm fixing the obvious problem, but removing the element isn't safe all the time as I wrote in the PR. Bill, do you know how to fix that

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Fix minor typo sace -> space

2018-03-15 Thread GerritHub
>From : supriti.si...@suse.com has uploaded this change for review. ( https://review.gerrithub.io/403932 Change subject: Fix minor typo sace -> space .. Fix minor typo sace -> space Change-Id: