Re: [PATCH 4/5] nvme: wait until all completed request's complete fn is called

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Ming Lei <ming.lei@xxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>
Subject: Re: [PATCH 4/5] nvme: wait until all completed request's complete fn is called
From: Sagi Grimberg <sagi@xxxxxxxxxxx>
Date: Tue, 23 Jul 2019 13:29:54 -0700
Cc: linux-block@xxxxxxxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx, Max Gurtovoy <maxg@xxxxxxxxxxxx>, Keith Busch <keith.busch@xxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>
In-reply-to: <20190722053954.25423-5-ming.lei@redhat.com>
References: <20190722053954.25423-1-ming.lei@redhat.com> <20190722053954.25423-5-ming.lei@redhat.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

Reviewed-by: Sagi Grimberg <sagi@xxxxxxxxxxx>

What about fc? I know that they are not canceling a request, but
they still complete it, shouldn't it also wait before removing?

Follow-Ups:
- Re: [PATCH 4/5] nvme: wait until all completed request's complete fn is called
  - From: Ming Lei

References:
- [PATCH 0/5] blk-mq: wait until completed req's complete fn is run
  - From: Ming Lei
- [PATCH 4/5] nvme: wait until all completed request's complete fn is called
  - From: Ming Lei

Prev by Date: Re: [PATCH 3/5] nvme: don't abort completed request in nvme_cancel_request
Next by Date: Re: [PATCH 5/5] blk-mq: remove blk_mq_complete_request_sync
Previous by thread: Re: [PATCH 4/5] nvme: wait until all completed request's complete fn is called
Next by thread: Re: [PATCH 4/5] nvme: wait until all completed request's complete fn is called
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux