[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: NFS4: allow reads and writes against delegations that have been recal...

>From Jeff Layton : Jeff Layton has uploaded this change for review. ( https://review.gerrithub.io/400650 Change subject: NFS4: allow reads and writes against delegations that have been recalled but not yet returned

Re: [Nfs-ganesha-devel] nfs ganesha vs nfs kernel performance

Hi, On Tue, Feb 20, 2018 at 8:12 AM, William Allen Simpson wrote: > On 2/18/18 2:47 PM, Matt Benjamin wrote: >> >> On Fri, Feb 16, 2018 at 11:23 AM, William Allen Simpson >>> >>> But the planned 2.7 improvements are mostly throughput related, not IOPS. >> >> >>

[Nfs-ganesha-devel] gtest results? profiles?

Now that we have a pile of nice gtests, who is compiling the results? Please post them here Also, DanG told me yesterday that he has a profile of the lookup test. Please post that here. That will allow us to better target the CPU bottlenecks.

Re: [Nfs-ganesha-devel] nfs ganesha vs nfs kernel performance

On 2/18/18 2:47 PM, Matt Benjamin wrote: On Fri, Feb 16, 2018 at 11:23 AM, William Allen Simpson But the planned 2.7 improvements are mostly throughput related, not IOPS. Not at all, though I am trying to ensure that we get async FSAL ops in. There are people working on IOPs too. async

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: "mdc_lookup" do not dispatch to FSAL

On 2/19/18 12:12 PM, Sachin Punadikar wrote: Hi Bill, I rechecked the logs & discussed with Daniel. I missed to see the log entries related to FSAL. So for this customer it looks like FSAL issue than a Ganesha issue Thanks for the update. The default log levels don't always show enough.