Displaying 3 results from an estimated 3 matches for "mas_set_rang".
Did you mean:
mas_set_range
2023 Mar 13
1
[PATCH drm-next v2 05/16] drm: manager to keep track of GPUs VA mappings
...o 0, see that it's NULL from 0 - 1, call
>>> mas_next() and get "a" from 1 - 3, write "a'" from 2 - 3:
>>>
>>> 0 1 a 2 a' 3
>>> broken: |-----|------|-----| (a is broken in this 1/2 step)
>>>
>>> mas_set_range(&mas, 0, 2); /* Resets the tree location to MAS_START */
>>> mas_store(&mas, b);
>>> 0 b 2 a' 3
>>> new: |-----------|-----| (b.bo_offset=m,a.bo_offset=n+2)
>>>
>>>
>>> You can *probably* also get away with thi...
2023 Feb 20
1
[PATCH drm-next v2 03/16] maple_tree: split up MA_STATE() macro
...look into your code yet.
Yes, I'm aware that I'd need to reset the whole iterator in order to
re-use it.
Regarding the other considerations of the iterator design please see my
answer to Matthew.
>
> We have methods of resetting the iterator and set the range (mas_set()
> and mas_set_range()) which are safe for what you are doing, but they
> will start the walk from the root node to the index again.
>
> So, if you know what you are doing is safe, then the way you have
> written it will work, but it's worth mentioning that this could occur.
>
> It is also wort...
2023 Mar 06
2
[PATCH drm-next v2 05/16] drm: manager to keep track of GPUs VA mappings
...ot; instead.
>
> Ah, so you could walk to 0, see that it's NULL from 0 - 1, call
> mas_next() and get "a" from 1 - 3, write "a'" from 2 - 3:
>
> 0 1 a 2 a' 3
> broken: |-----|------|-----| (a is broken in this 1/2 step)
>
> mas_set_range(&mas, 0, 2); /* Resets the tree location to MAS_START */
> mas_store(&mas, b);
> 0 b 2 a' 3
> new: |-----------|-----| (b.bo_offset=m,a.bo_offset=n+2)
>
>
> You can *probably* also get away with this:
>
> walk to 0, see that it's NULL...