Sorry, got the terminology wrong. I mean the "Compare and Write" fused operation in 6.2.1.
The way I see it, I have to ensure that both requests end up right after each other in the same queue, so I have to lock the queue, submit both, and at least rudimentarily advise the cache manager of what these requests mean. I'd like to cache the written metadata
so future request processing can reuse it after the write has indicated success. If I have more higher-level requests queued, that is somewhat easy because I can pass the data on internally, but if there is a pause in request processing the metadata blocks
should take part in normal cache handling.
