All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Junichi Nomura <j-nomura@ce.jp.nec.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH for 4.1-rc] dm: run queue on re-queue
Date: Tue, 26 May 2015 09:09:17 -0400	[thread overview]
Message-ID: <20150526130916.GB16369@redhat.com> (raw)
In-Reply-To: <55642E11.6010500@ce.jp.nec.com>

On Tue, May 26 2015 at  4:25P -0400,
Junichi Nomura <j-nomura@ce.jp.nec.com> wrote:

> Without kicking queue, requeued request may stay forever in
> the queue if there are no other I/O activities to the device.
> 
> The original error had been in v2.6.39 with commit 7eaceaccab5f
> ("block: remove per-queue plugging"), which replaced conditional
> plugging by periodic runqueue.
> 
> Commit 9d1deb83d489 in v4.1-rc1 removed the periodic runqueue
> and the problem started to manifest.
> 
> Fixes: 9d1deb83d489 ("dm: don't schedule delayed run of the queue if nothing to do")
> Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
> 
> diff --git a/drivers/md/dm.c b/drivers/md/dm.c
> index a930b72..0bf79a0 100644
> --- a/drivers/md/dm.c
> +++ b/drivers/md/dm.c
> @@ -1164,6 +1164,7 @@ static void old_requeue_request(struct request *rq)
>  
>  	spin_lock_irqsave(q->queue_lock, flags);
>  	blk_requeue_request(q, rq);
> +	blk_run_queue_async(q);
>  	spin_unlock_irqrestore(q->queue_lock, flags);
>  }

Thanks Junichi.  The new blk-mq path did kick the queue, but obviously
the old request_fn path didn't.  I'll get this queued for 4.1.

Mike

      reply	other threads:[~2015-05-26 13:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  8:25 [PATCH for 4.1-rc] dm: run queue on re-queue Junichi Nomura
2015-05-26 13:09 ` Mike Snitzer [this message]

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=20150526130916.GB16369@redhat.com \
    --to=snitzer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=j-nomura@ce.jp.nec.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.