Messages in this thread | | | Date | Thu, 19 Jul 2018 23:43:29 -0700 (PDT) | Subject | Re: [PATCH - revised] rhashtable: detect when object movement might have invalidated a lookup | From | David Miller <> |
| |
From: NeilBrown <neilb@suse.com> 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.
Thanks.
| |