2

I'm trying to use radix tree to maintain one internal data for the driver. So what's the proper way to destroy the whole tree?

One thought is to traverse the tree with the method mentioned at: 1

For each node, free the item and delete its key from the tree.

The other question is, is radix_tree_for_each_slot() safe with delete item inside the loop? Will delete trigger internal shrink and cause iteration failure?

Community
  • 1
  • 1
Eric
  • 471
  • 4
  • 9

1 Answers1

2

Check out cgwb_bdi_unregister.

It seems to be doing pretty much what you need - it iterates over the radix tree with radix_tree_for_each_slot() and while doing so it does also radix_tree_delete (from cgwb_kill).

So I guess nothing should blow up if you're keeping things properly synchronized.

t123yh
  • 657
  • 2
  • 7
  • 18
dragosht
  • 3,237
  • 2
  • 23
  • 32
  • How about radix tree itself? Or say, is radix_tree_delete the only operation to destroy the tree? – Eric Dec 16 '15 at 17:35
  • 1
    OK, originally I was worry about radix_tree_node_cachep created by kmem_cache_create. It seems there is only one cahcep created at init time, and all trees share the same one, then no need and should not destroy it. Thanks! – Eric Dec 16 '15 at 17:38
  • 1
    For those who can't find it: `cgwb_bdi_destroy` has been renamed to `cgwb_bdi_unregister`. – t123yh Dec 31 '18 at 11:40