tag-returning: Adopted tag-returns in mdir/mtree namelookup

- lfs3_mdir_namelookup
- lfs3_mtree_namelookup

These are interesting, because, unlike lfs3_rbyd_namelookup, we don't
care about how query mids compare with the found mid.

Adopting tag-returns does mean we no longer return the relevant tag
when the query mid is missing, but the fact that the tests are passing
means this is a non-issue.

Shaves off a bit more code:

           code          stack          ctx
  before: 36260           2336          656
  after:  36216 (-0.1%)   2336 (+0.0%)  656 (+0.0%)

Maybe these should have been updated in lock-step with
lfs3_mtree_pathlookup, but lfs3_mtree_pathlookup is going to impact a
lot more code...
This commit is contained in:
Christopher Haster
2025-07-17 16:42:45 -05:00
parent a549654618
commit f9d7885edc
2 changed files with 214 additions and 214 deletions
+162 -162
View File
File diff suppressed because it is too large Load Diff