All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v1 2/3] nvme: Use blk-mq helper for IO termination
Date: Wed, 3 Feb 2016 01:26:39 +0000	[thread overview]
Message-ID: <20160203012638.GC21046@localhost.localdomain> (raw)
In-Reply-To: <BJXPR01MB1999CBB2644C70CE07E4B28E0D00@BJXPR01MB199.CHNPR01.prod.partner.outlook.cn>

On Wed, Feb 03, 2016@12:35:55AM +0000, Wenbo Wang wrote:
> After canceling these requests, the requests and tags are freed. If queues are restarted shortly, these already freed requests will be queue_rq again? This seems not correct.

That's not true. We only set DNR if the queue is dead. Otherwise the
requests are eligible for requeuing if they haven't exceeded total time.

  reply	other threads:[~2016-02-03  1:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 12:44 [PATCH RESEND v1 0/3] Move active IO termination to the core Sagi Grimberg
2016-02-02 12:44 ` [PATCH v1 1/3] blk-mq: Export tagset iter function Sagi Grimberg
2016-02-02 12:44 ` [PATCH v1 2/3] nvme: Use blk-mq helper for IO termination Sagi Grimberg
2016-02-02 16:32   ` Wenbo Wang
2016-02-02 16:49     ` Keith Busch
2016-02-03  0:35       ` Wenbo Wang
2016-02-03  1:26         ` Keith Busch [this message]
2016-02-04 14:28           ` Wenbo Wang
2016-02-04 15:44             ` Keith Busch
2016-02-05  6:53               ` Wenbo Wang
2016-02-02 12:44 ` [PATCH v1 3/3] blk-mq: Make blk_mq_all_tag_busy_iter static Sagi Grimberg
2016-02-10 10:12 ` [PATCH RESEND v1 0/3] Move active IO termination to the core Sagi Grimberg
2016-03-09 14:32   ` Christoph Hellwig
2016-03-09 15:57     ` Sagi Grimberg
  -- strict thread matches above, loose matches on Subject: below --
2016-01-10  8:59 [PATCH " Sagi Grimberg
2016-01-10  8:59 ` [PATCH v1 2/3] nvme: Use blk-mq helper for IO termination Sagi Grimberg
2016-01-15 16:48   ` Keith Busch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160203012638.GC21046@localhost.localdomain \
    --to=keith.busch@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.