[PATCHv9 RFC 1/3] Break up monolithic iommu table/lock into finer graularity pools and lock

[Sowmini Varadhan]

On (04/05/15 22:26), Benjamin Herrenschmidt wrote:
> 
> So you decided to keep the logic here that updates the hint instead of
> just getting rid of need_flush alltogether ?
> 
> Out of curiosity, what's the rationale ? Did you find a reason why
> resetting the hint in those two cases (rather than just setting "start"
> appropriately) is actually useful ?

To be honest, I actually did not want to poke at this too much, given
that both ppc and sparc seem to have essentially the same
logic.

But my gut feeling is that if the pool->hint hasn't resulted
in a succesful area_alloc, we might as well reset it for the next
iommu*range_alloc-er, because it's likely that the next alloc
will also need to  wrap and search anyway..

--Sowmini