Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the following link: https://bugzilla.lustre.org/show_bug.cgi?id=11270
(In reply to comment #19) > Wow, nice to get this. Shouldn't this become the default setting? too small to be default i think. anyway no performance testing is done yet. > I am > surprised that the server doesn't enforce this, it seems you are setting > client options? client makes its own decisions based on the request size. according the HLD client doesn't talk with the server if the request size is smaller than the min_nolock_size. more precisely client behaves differently for small, medium and large requests: 1. small requests. request size < min_nolock_size client _always_ goes lockless i/o, the server is not asked. 2. medium size requests. min_nolock_size <= rq. size <= max_nolock_size client asks the server whether lockless i/o is used and caches a positive answer for contention_time seconds -- subsequent medium size requests will use lockless i/o. 3. large requests. rq.size > max_nolock_size always ask the server, do not cache the answer. _______________________________________________ Lustre-devel mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-devel
