On 17.06.2024 13:18, Andrew Cooper wrote:
> On 17/06/2024 10:54 am, Jan Beulich wrote:
>> On 14.06.2024 19:07, Andrew Cooper wrote:
>>> More fallout from looking at the code generation...
>>>
>>> for_each_set_bit() forces it's bitmap parameter out into memory. For an
>>> arbitrary sized bitmap, th
On 17/06/2024 10:54 am, Jan Beulich wrote:
> On 14.06.2024 19:07, Andrew Cooper wrote:
>> More fallout from looking at the code generation...
>>
>> for_each_set_bit() forces it's bitmap parameter out into memory. For an
>> arbitrary sized bitmap, this is fine - and likely preferable as it's an
>>
On 14.06.2024 19:07, Andrew Cooper wrote:
> More fallout from looking at the code generation...
>
> for_each_set_bit() forces it's bitmap parameter out into memory. For an
> arbitrary sized bitmap, this is fine - and likely preferable as it's an
> in-memory to begin with.
>
> However, more than
More fallout from looking at the code generation...
for_each_set_bit() forces it's bitmap parameter out into memory. For an
arbitrary sized bitmap, this is fine - and likely preferable as it's an
in-memory to begin with.
However, more than half the current users of for_each_set_bit() are
operati
