[lkml]   [2018]   [Jul]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH - revised] rhashtable: detect when object movement might have invalidated a lookup
On Thu, Jul 19 2018, David Miller wrote:

> From: NeilBrown <>
> Date: Fri, 20 Jul 2018 16:30:34 +1000
>> Does this ruling also apply to the bit-spin-lock changes and the
>> per-cpu-counter changes that I have proposed? These improve
>> scalability when updates dominate. Not having these in mainline
>> would mean I need to carry a separate rhashtables implementation for
>> lustre, which means code diversion which isn't healthy in the long
>> run.
> If it helps existing rhashtable users generally, then it is fine,
> since it will actually be tested by upstream users.

Good, thanks.

[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2018-07-20 09:10    [W:0.075 / U:4.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site