On 3/6/17 2:17 PM, Frank Filz wrote:
>> [...]
>> The next set of patches affect the epoll and per-connection setup.
>> I've tried this in the past, and never gotten it to work properly.
>> It will take awhile and be disruptive to both ntirpc and ganesha.
>>
>> Also, I'd like to port the I/O processing that I'd written for RDMA to
>> TCP (andprobably UDP).  That's a lot of work, too.
>>
>> In conclusion, I'm advocating that we tag V2.5 (ntirpc 1.5) very soon,
>> so the -fc process can shake out any bugs and allow tuning, before we
>> embark on the next significant steps.
>
> Yes, I'd like to get the dirent chunking in also.
>
Cool.  That will likely require a bit of debugging and tuning, too.
But the performance improvement will likely be significant.

So let's put that feature in this week, even though not perfected, and
spend 2 or 3 -fc cycles fumigating the bugs.  Then ship!

It's a little bit later than we'd originally planned (that is, before
Connect-a-thon), but hopefully timely enough that folks can roll out
in their semi-annual distributions.

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Reply via email to