On 6/17/25 07:33, Bart Van Assche wrote: > Prepare for preserving the order of pipelined zoned writes per zone. I do not understand why that is needed. And the commit message does not explain anything. I suspect it is to handle the case where a submitter changes CPU when issuing writes to a zone. But if that is the case, you should be able to hide that explicit CPU choice within the blk-zoned code instead of exposing it through the API. E.g.: plug the bio and schedule the BIO work to run on the CPU you want. -- Damien Le Moal Western Digital Research
