dmu_tx: rename dmu_tx_assign() flags from TXG_* to DMU_TX_*

[robn]

[Sponsors: Klara, Inc., Wasabi Technology, Inc.]

Motivation and Context

On its own, helps to avoid confusion with the similarly-named txg_wait_synced().

But actually, at Klara there's a couple of active development projects (at least forced export (#11082), some more work around fsync()) that will want to extend txg_wait_synced() to also have flags describing the conditions it may exit. For these, we've settled on TXG_WAIT_* as the obvious name for such flags, and we want to reclaim that namespace.

Description

Mechanical replacement of TXG_* with DMU_TX_*.

How Has This Been Tested?

This version compile-checked only, though it is in heavy use in our internal projects as well.

Since it's just renaming three (+1 in ztest) numeric defines, I don't expect anything of interest.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

[amotin]

Wish it was not so invasive...

[robn]

Yeah, bit noisy but at least we only have to do it once.

[oshogbo]

LGTM.

[amotin]

@oshogbo There is "Review changes" button on the "Files changed" tab. ;)