From mboxrd@z Thu Jan 1 00:00:00 1970 From: sagi@grimberg.me (Sagi Grimberg) Date: Fri, 24 May 2019 01:15:42 -0700 Subject: [PATCH 5.0 66/95] nvme: cancel request synchronously In-Reply-To: <20190521124908.GA655@ming.t460p> References: <20190509181309.180685671@linuxfoundation.org> <20190509181314.082604502@linuxfoundation.org> <20190521094535.GA28632@ming.t460p> <7a4863ba-ece9-e3fa-8396-21736d54e1fe@mellanox.com> <20190521104121.GA31530@ming.t460p> <23729cbc-3a3f-fe16-be14-71053253c53b@mellanox.com> <20190521124908.GA655@ming.t460p> Message-ID: <09c806a8-7be8-3552-265b-d651aaf848e8@grimberg.me> >> is there an API in the block layer to guaranty that ? > > So far there isn't yet. > > And it can be built easily against blk_mq_tagset_busy_iter(), then called > in delay-spin style for checking if there is any request marked as > MQ_RQ_COMPLETE. This will probably make blk_mq_complete_request_sync() redundant wouldn't it?