From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Pishioneri Subject: Re: NFS over RDMA benchmark Date: Thu, 25 Apr 2013 15:01:33 -0400 Message-ID: <51797D8D.1080302@psu.edu> References: <0EE9A1CDC8D6434DB00095CD7DB873462CF96C65@MTLDAG01.mtl.com> <62745258-4F3B-4C05-BFFD-03EA604576E4@ornl.gov> <0EE9A1CDC8D6434DB00095CD7DB873462CF9715B@MTLDAG01.mtl.com> <20130423210607.GJ3676@fieldses.org> <0EE9A1CDC8D6434DB00095CD7DB873462CF988C9@MTLDAG01.mtl.com> <20130424150540.GB20275@fieldses.org> <20130424152631.GC20275@fieldses.org> <517823E0.4000402@talpey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Wendy Cheng Cc: Tom Talpey , "J. Bruce Fields" , Yan Burman , "Atchley, Scott" , Tom Tucker , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Or Gerlitz List-Id: linux-rdma@vger.kernel.org On 4/25/13 1:18 PM, Wendy Cheng wrote: > On Wed, Apr 24, 2013 at 11:26 AM, Tom Talpey wrote: >> 1) >> >> The client slot count is not hard-coded, it can easily be changed by >> writing a value to /proc and initiating a new mount. But I doubt that >> increasing the slot table will improve performance much, unless this is >> a small-random-read, and spindle-limited workload. > It was a shot in the dark :) .. as our test bed has not been setup > yet .However, since I'll be working on (very) slow clients, increasing > this buffer is still interesting (to me). I don't see where it is > controlled by a /proc value (?) - but that is not a concern at this > moment as /proc entry is easy to add. More questions on the server > though (see below) ... Might there be confusion between the RDMA slot table and the TCP/UDP ones (which have proc entries under /proc/sys/sunrpc)? -Phil -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html