Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3164858imj; Mon, 11 Feb 2019 15:18:12 -0800 (PST) X-Google-Smtp-Source: AHgI3IbJjiz1vWkpp7+ztYkbecrxIpyyoGueOb3gbGCpKuusZlTdLpEy5CK1plqjS888RB46KO+b X-Received: by 2002:a65:6242:: with SMTP id q2mr685926pgv.245.1549927091972; Mon, 11 Feb 2019 15:18:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549927091; cv=none; d=google.com; s=arc-20160816; b=tNZ2X+YuX/VVpm4378jsndV4aDIaNXOX5fZ0odOZ9yyeHbVaOoVfqFk9emz5uYMzZh DI3F6vF3Nv4QaYDuxQtGmdyrypFq0fqzJovinx0d9MarHiW0Ls2s4A7AfM3uJFJwVMXe hIbCgfO995W2EShvMDRWqsPe3E/aRXSb97eqbtOVmpaQp3YpHt88XMwYAIs1dBbVYJmo lRPwThN9DD5HqvcAKVh76I3d43YlCG1NLUKMT07mc7BzLEBE5tQbZV06XSAj+Y0XjLZZ JBBBiOuwuFgcgpnDvF/aj2dUxCzC1wGhKiBbVu12PBotU8T04/TAG4z6uez67xEGprb8 lbKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject:dkim-signature; bh=oTcqWST6FEXJ74L2S+lCuUw15fC4Ilj/dXbcjgcG3xM=; b=UGhVzvj/Hl0EVVfrchzsPZG3GJ1s9G19svOloJeGlxMe9sNaMTmJJERzYoux/YA3+N xukL5BbUqoZpuGz8nL4rpMpclxOC8J+mFJW4E6cjdCQbdb93jvVMjKQjuf83u3MOW/NT U6CDGNmLzUrt0s9twlMAK2+F9G6WV/xFgEtRsEQvfOqiAYqLC6uZ6pk6NvPz3LyC1fJH g1GrpUVUDLA1mP/dLp+w0YlkccXGbjZ9v4jBB6nbcguQ7u4B57Cjn9srLv4E718oZ+ft 8WuoEDAb29DnE0fmYGIiswr0JBO2hUuwT9s2YW6kE1Ph+1KX8SP7ym+LdwBiQ4+TBhoo AA4A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b="PjyK/zne"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m2si10546226plt.98.2019.02.11.15.17.56; Mon, 11 Feb 2019 15:18:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b="PjyK/zne"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727183AbfBKXPs (ORCPT + 99 others); Mon, 11 Feb 2019 18:15:48 -0500 Received: from mail-pl1-f196.google.com ([209.85.214.196]:33507 "EHLO mail-pl1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726949AbfBKXPs (ORCPT ); Mon, 11 Feb 2019 18:15:48 -0500 Received: by mail-pl1-f196.google.com with SMTP id y10so305670plp.0 for ; Mon, 11 Feb 2019 15:15:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=oTcqWST6FEXJ74L2S+lCuUw15fC4Ilj/dXbcjgcG3xM=; b=PjyK/zne0r0uU0KjFb2MjfOUEgPt4FBbq3g29lo58TfUVF2glXRcTZCtb9vd6WmgLW V/oLi72B6NcncK39FwgcumOXs/P5vaX7Gqc3B7aJMVq7ysq9xG9aMRfJXG3gbOHxCF0Y rhDtp8UUsWci5fnsHx3/GkswWqP3/dn3dzz6cljCzP4wA59DRlZZhSzNIbQfMO8x2ECD 0trsoIO23nue9tiKe4o2Jl06J+ytaT0oKfXWJcRzToVA8pB3mfkNPEp0nTnyhsokrSK8 fHMix1/jCQCqE1pNWP0YL1t6uwcR1/DNHMBL9GaKFRVAFbtVFoKBi+vLZDLpoIEtDxJ9 CfPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=oTcqWST6FEXJ74L2S+lCuUw15fC4Ilj/dXbcjgcG3xM=; b=mFiRpL440fsB3x2pyyC9ONXK/rkLgBcSEJee8IDOLhu9QVJMpo6Na5R6aOvA8TPppu TxabXP+UD3WA7I5w47HaOPYZj6DAYSnuef6J+2mbAQJpavfG3TDgVLsyzJ3kzjKyWpog E7Mbuf07Chd2bhnjBG+rM7YekVlUdd+fnzEo/qIHFiHkyFbiXGoBeY/dCpndLJpAb1tP cQFtiXCEKYeTfw8UBgHZLfStCj7Un4sFo0HwLUj2Kav7WCKNqNCZdPkZK3wRnZx11pwZ GQHN9YVRjq5tGs2crzKbrxYRiAVVQt+weTA+o+DEgCbZNjlIF3Ksb8tdvh0gpGy93VzE sAGg== X-Gm-Message-State: AHQUAubt/MTTd4yjP+Q6JTgWvPtR3UOaGMWdvyI2dkbUko9SBxKFOikw X4DIdnZr73dh5U6DDzEgVM7yG/ccqP+Smg== X-Received: by 2002:a17:902:b214:: with SMTP id t20mr762524plr.248.1549926947026; Mon, 11 Feb 2019 15:15:47 -0800 (PST) Received: from [192.168.1.121] (66.29.188.166.static.utbb.net. [66.29.188.166]) by smtp.gmail.com with ESMTPSA id g128sm8693659pfb.121.2019.02.11.15.15.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Feb 2019 15:15:46 -0800 (PST) Subject: Re: [PATCH] blk-mq: insert rq with DONTPREP to hctx dispatch list when requeue From: Jens Axboe To: Jianchao Wang Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org References: <1549863665-1691-1-git-send-email-jianchao.w.wang@oracle.com> <937e9207-dcf7-dab5-1917-8a10303edc67@kernel.dk> Message-ID: <82deee13-a4ff-9bf5-5e01-0e4df01b7ff7@kernel.dk> Date: Mon, 11 Feb 2019 16:15:44 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <937e9207-dcf7-dab5-1917-8a10303edc67@kernel.dk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/11/19 8:59 AM, Jens Axboe wrote: > On 2/10/19 10:41 PM, Jianchao Wang wrote: >> When requeue, if RQF_DONTPREP, rq has contained some driver >> specific data, so insert it to hctx dispatch list to avoid any >> merge. Take scsi as example, here is the trace event log (no >> io scheduler, because RQF_STARTED would prevent merging), >> >> kworker/0:1H-339 [000] ...1 2037.209289: block_rq_insert: 8,0 R 4096 () 32768 + 8 [kworker/0:1H] >> scsi_inert_test-1987 [000] .... 2037.220465: block_bio_queue: 8,0 R 32776 + 8 [scsi_inert_test] >> scsi_inert_test-1987 [000] ...2 2037.220466: block_bio_backmerge: 8,0 R 32776 + 8 [scsi_inert_test] >> kworker/0:1H-339 [000] .... 2047.220913: block_rq_issue: 8,0 R 8192 () 32768 + 16 [kworker/0:1H] >> scsi_inert_test-1996 [000] ..s1 2047.221007: block_rq_complete: 8,0 R () 32768 + 8 [0] >> scsi_inert_test-1996 [000] .Ns1 2047.221045: block_rq_requeue: 8,0 R () 32776 + 8 [0] >> kworker/0:1H-339 [000] ...1 2047.221054: block_rq_insert: 8,0 R 4096 () 32776 + 8 [kworker/0:1H] >> kworker/0:1H-339 [000] ...1 2047.221056: block_rq_issue: 8,0 R 4096 () 32776 + 8 [kworker/0:1H] >> scsi_inert_test-1986 [000] ..s1 2047.221119: block_rq_complete: 8,0 R () 32776 + 8 [0] >> >> (32768 + 8) was requeued by scsi_queue_insert and had RQF_DONTPREP. >> Then it was merged with (32776 + 8) and issued. Due to RQF_DONTPREP, >> the sdb only contained the part of (32768 + 8), then only that part >> was completed. The lucky thing was that scsi_io_completion detected >> it and requeued the remaining part. So we didn't get corrupted data. >> However, the requeue of (32776 + 8) is not expected. > > Good catch, but how about something like this? Makes it more integrated, > I think that's cleaner. This is probably better (and safer): diff --git a/block/blk-mq.c b/block/blk-mq.c index 8f5b533764ca..b3908eb3881c 100644 --- a/block/blk-mq.c +++ b/block/blk-mq.c @@ -737,12 +737,21 @@ static void blk_mq_requeue_work(struct work_struct *work) spin_unlock_irq(&q->requeue_lock); list_for_each_entry_safe(rq, next, &rq_list, queuelist) { - if (!(rq->rq_flags & RQF_SOFTBARRIER)) + if (!(rq->rq_flags & (RQF_SOFTBARRIER | RQF_DONTPREP))) continue; rq->rq_flags &= ~RQF_SOFTBARRIER; list_del_init(&rq->queuelist); - blk_mq_sched_insert_request(rq, true, false, false); + + /* + * If RQF_DONTPREP is set, rq may contain some driver + * specific data. Insert it to hctx dispatch list to avoid + * any merge. + */ + if (rq->rq_flags & RQF_DONTPREP) + blk_mq_sched_insert_request(rq, true, false, false); + else + blk_mq_request_bypass_insert(rq, false); } while (!list_empty(&rq_list)) { -- Jens Axboe