-----Original Message-----
From: Matt Benjamin [mailto:mbenjami@redhat.com]
Sent: Friday, September 14, 2018 11:01 PM
To: Malahal Naineni <malahal(a)gmail.com>
Cc: Kropelin, Adam <kropelin(a)amazon.com>; William Allen Simpson
<william.allen.simpson(a)gmail.com>; devel(a)lists.nfs-ganesha.org
Subject: Re: [NFS-Ganesha-Devel] Re: Scalability issue with VFS FSAL and
large amounts of read i/o in flight
That's how it was when the ioq was introduced. I think Daniel has a
fix in mind, but by all means, send this too.
Matt
On Fri, Sep 14, 2018 at 10:42 PM, Malahal Naineni <malahal(a)gmail.com>
wrote:
> I was working with 2.5 originally and wanted to see a fix with minimal
> changes. The patch was supposed to be Work In Progress but was
> squashed down as I didn't have enough arguments to back it up (ended
> up with a timeout patch). Now, we have systems in the lab exhibiting
> this in-house and customer locations as well (I added IOQ stats and
> they showed 1-second latency from queuing to calling writev alone under
stress).
>
> I would put the IOQ in xprt itself as you did. Please post the patch
> and let us review it.
See attached for the changes I'm testing with. Let me know if this should go to
gerrithub or elsewhere.
This is against v1.5.5 but is trivially adapted to -next.
--Adam