On Wed, Jan 22, 2025 at 11:43 AM Vlastimil Babka <vbabka@xxxxxxx> wrote: [...] > > __is_kvfree_rcu_offset() and its usage from Tiny. Granted, there is > > the overhead of function calling, but I highly doubt that it is going > > to be a bottleneck, considering that the __is_kvfree_rcu_offset() path > > is a kfree slow-path. I feel in the long run, this will also be more > > maintainable. > > > > Or is there a reason other than the theoretical function call overhead > > why this may not work? > > My concern was about the overhead of calculating the pointer to the object > starting address, but it's just some arithmetics, so it should be > negligible. So I'm prototyping this approach now. Thanks all. Ah, that's a valid point. Looking forward to reviewing the patch and hope it works out! thanks, - Joel