Re: [Nfs-ganesha-devel] dispatch queues

2017-03-10 Thread William Allen Simpson
On 3/9/17 10:22 AM, Matt Benjamin wrote: >> From: "William Allen Simpson" >> After a somewhat loud discussion with Matt, we've agreed on a >> different approach. This will also be useful for fully async IO >> that is planned for V2.6. > > Um, I don't think this statement represents either of the

Re: [Nfs-ganesha-devel] dispatch queues

2017-03-09 Thread Malahal Naineni
>> Nothing as invasive as queuing changes should go >> into 2.5. 2.5 should get the dirent chunking and bug fixes only at this >> point. Agree with Dan. Let us put out 2.5, and have these fixes for 2.6. Regards, Malahal. On Thu, Mar 9, 2017 at 8:39 PM, Daniel Gryniewicz wrote: > On 03/09/2017

Re: [Nfs-ganesha-devel] dispatch queues

2017-03-09 Thread Matt Benjamin
Hi Bill, - Original Message - > From: "William Allen Simpson" > To: "NFS Ganesha Developers" > Sent: Thursday, March 9, 2017 2:44:29 AM > Subject: Re: [Nfs-ganesha-devel] dispatch queues > > On 3/8/17 5:34 AM, William Allen Simpson wrote: > >

Re: [Nfs-ganesha-devel] dispatch queues

2017-03-09 Thread Daniel Gryniewicz
On 03/09/2017 02:44 AM, William Allen Simpson wrote: > On 3/8/17 5:34 AM, William Allen Simpson wrote: >> Ganesha currently has 2 phases of dispatch queuing: one for input and >> decoding, then another for executing/encoding output. (I've fixed the >> third queue for later sending the output, wher

Re: [Nfs-ganesha-devel] dispatch queues

2017-03-08 Thread William Allen Simpson
On 3/8/17 5:34 AM, William Allen Simpson wrote: > Ganesha currently has 2 phases of dispatch queuing: one for input and > decoding, then another for executing/encoding output. (I've fixed the > third queue for later sending the output, where the thread should stay > hot as long as there's more to