On Fri, Sep 27, 2019 at 01:17:52PM -0400, Brian Foster wrote: > The upcoming allocation algorithm update searches multiple > allocation btree cursors concurrently. As such, it requires an > active state to track when a particular cursor should continue > searching. While active state will be modified based on higher level > logic, we can define base functionality based on the result of > allocation btree lookups. > > Define an active flag in the private area of the btree cursor. > Update it based on the result of lookups in the existing allocation > btree helpers. Finally, provide a new helper to query the current > state. I vaguely remember having the discussion before, but why isn't the active flag in the generic part of xfs_btree_cur and just tracked for all types? That would seem bother simpler and more useful in the long run.
