mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ming Lin <ming.l@ssi.samsung.com>,
	Kent Overstreet <kent.overstreet@gmail.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v1 5/6] blk-mq: fix for trace_block_plug()
Date: Mon, 19 Oct 2015 13:59:11 -0400	[thread overview]
Message-ID: <x49oafun3io.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CACVXFVNuLBTUQFDMdkykJvbKLV_e0EPGuM1gJ71FRVO0b6ujYg@mail.gmail.com> (Ming Lei's message of "Mon, 19 Oct 2015 23:58:39 +0800")

Ming Lei <ming.lei@canonical.com> writes:

> On Mon, Oct 19, 2015 at 11:38 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
>> Ming Lei <ming.lei@canonical.com> writes:
>>
>>> The trace point is for tracing plug event of each request
>>> queue instead of each task, so we should check the request
>>> count in the plug list from current queue instead of
>>> current task.
>>
>> If blk_queue_nomerges returns true, request_count won't be updated, so
>> you've essentially broken plugging for those queues.
>
> Yes, you are right, and blk_queue_bio() has the same problem too,
> and looks automatic flush plug can't work for nomerges queue at all.

Hi Ming,

Something like this would fix it.  Feel free to add it into your patch
set if you're going to do another spin.  Otherwise I'll just send it off
separately.

-Jeff

From: Jeff Moyer <jmoyer@redhat.com>
Subject: block: fix plug list flushing for nomerge queues

Request queues with merging disabled will not flush the plug list after
BLK_MAX_REQUEST_COUNT requests have been queued, since the code relies
on blk_attempt_plug_merge to compute the request_count.  Fix this by
computing the number of queued requests even for nomerge queues.

Signed-off-by: Jeff Moyer <jmoyer@redhat.com>

diff --git a/block/blk-core.c b/block/blk-core.c
index 2eb722d..f0ae087 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -1594,6 +1594,30 @@ out:
 	return ret;
 }
 
+unsigned int blk_plug_queued_count(struct request_queue *q)
+{
+	struct blk_plug *plug;
+	struct request *rq;
+	struct list_head *plug_list;
+	unsigned int ret = 0;
+
+	plug = current->plug;
+	if (!plug)
+		goto out;
+
+	if (q->mq_ops)
+		plug_list = &plug->mq_list;
+	else
+		plug_list = &plug->list;
+
+	list_for_each_entry(rq, plug_list, queuelist) {
+		if (rq->q == q)
+			ret++;
+	}
+out:
+	return ret;
+}
+
 void init_request_from_bio(struct request *req, struct bio *bio)
 {
 	req->cmd_type = REQ_TYPE_FS;
@@ -1641,9 +1665,11 @@ static void blk_queue_bio(struct request_queue *q, struct bio *bio)
 	 * Check if we can merge with the plugged list before grabbing
 	 * any locks.
 	 */
-	if (!blk_queue_nomerges(q) &&
-	    blk_attempt_plug_merge(q, bio, &request_count, NULL))
-		return;
+	if (!blk_queue_nomerges(q)) {
+		if (blk_attempt_plug_merge(q, bio, &request_count, NULL))
+			return;
+	} else
+		request_count = blk_plug_queued_count(q);
 
 	spin_lock_irq(q->queue_lock);
 
diff --git a/block/blk-mq.c b/block/blk-mq.c
index 7785ae9..604a1f3 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -1267,9 +1267,12 @@ static void blk_mq_make_request(struct request_queue *q, struct bio *bio)
 
 	blk_queue_split(q, &bio, q->bio_split);
 
-	if (!is_flush_fua && !blk_queue_nomerges(q) &&
-	    blk_attempt_plug_merge(q, bio, &request_count, &same_queue_rq))
-		return;
+	if (!is_flush_fua && !blk_queue_nomerges(q)) {
+		if (blk_attempt_plug_merge(q, bio, &request_count,
+					   &same_queue_rq))
+			return;
+	} else
+		request_count = blk_plug_queued_count(q);
 
 	rq = blk_mq_map_request(q, bio, &data);
 	if (unlikely(!rq))
diff --git a/block/blk.h b/block/blk.h
index 98614ad..aa27d02 100644
--- a/block/blk.h
+++ b/block/blk.h
@@ -86,6 +86,7 @@ bool bio_attempt_back_merge(struct request_queue *q, struct request *req,
 bool blk_attempt_plug_merge(struct request_queue *q, struct bio *bio,
 			    unsigned int *request_count,
 			    struct request **same_queue_rq);
+unsigned int blk_plug_queued_count(struct request_queue *q);
 
 void blk_account_io_start(struct request *req, bool new_io);
 void blk_account_io_completion(struct request *req, unsigned int bytes);


  reply	other threads:[~2015-10-19 17:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 15:52 [PATCH v1 0/6] block: some misc changes Ming Lei
2015-10-17 15:52 ` [PATCH v1 1/6] block: setup bi_phys_segments after splitting Ming Lei
2015-10-17 15:52 ` [PATCH v1 2/6] block: avoid to merge splitted bio Ming Lei
2015-10-17 15:52 ` [PATCH v1 3/6] blk-mq: check bio_mergeable() early before merging Ming Lei
2015-10-19 15:11   ` Jeff Moyer
2015-10-17 15:52 ` [PATCH v1 4/6] block: " Ming Lei
2015-10-19 15:27   ` Jeff Moyer
2015-10-19 15:32     ` Ming Lei
2015-10-19 15:46       ` Jeff Moyer
2015-10-17 15:52 ` [PATCH v1 5/6] blk-mq: fix for trace_block_plug() Ming Lei
2015-10-19 15:38   ` Jeff Moyer
2015-10-19 15:58     ` Ming Lei
2015-10-19 17:59       ` Jeff Moyer [this message]
2015-10-20  0:38         ` Ming Lei
2015-10-17 15:52 ` [PATCH v1 6/6] blk-mq: mark ctx as pending at batch in flush plug path Ming Lei
2015-10-19 15:57   ` Jeff Moyer

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=x49oafun3io.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.l@ssi.samsung.com \
    --cc=ming.lei@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®