Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2884267ybc; Wed, 20 Nov 2019 23:15:36 -0800 (PST) X-Google-Smtp-Source: APXvYqzFn7tPXl5/CgI/1s/WDrSc7VK82we15lUK1eo6oZ59VOmDwj3czt79TeyBaWmaxeZMeuFl X-Received: by 2002:a17:906:b6c3:: with SMTP id ec3mr12010378ejb.27.1574320536585; Wed, 20 Nov 2019 23:15:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574320536; cv=none; d=google.com; s=arc-20160816; b=NM3cf3MNuiYdTV+IGIxOQXzij/DqEIyxR8KAVUnBTTw/xPnA5UWHaWJxySYWneOrxw our/H3QXCCpSvosVPbw4VUCFj7n+lqj9xkUDDZp6ymf1kDAe32NBQiLiNRDD84RduOPp 4TmNbYliU4ldQ9ZcITE4o93bLfJbMvWiDjO8OcHXFGdjeGsfglzB4kSFmfYVvcOHowJj pWVY0rjGOlNSskqHx+uIZozHsDG0S6Xjktq/q0spYI0X3KVRWf8TsNIxOlJhPdDYqYUj 60iMi+PZT+MmiOJTvW7jKkNkmTE5ab3sg471GAQKRxI0MQSipm+ks8QvnwhWszHTPxNi pP+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:user-agent:subject:cc:to:from :date:content-transfer-encoding:mime-version:dkim-signature; bh=xL3ut0Gb5LSFbLI5E9f4K9lAtbTVA7+YunIPYZDbV+o=; b=O9jSJq25tOxDk8WShUQQeDdebexFunp7ljM/e4UZXnjenz31MIdSjcobL12O9+fuUj hBIjCEnFr8YayFy7lZETwG0hjw2fyrE5Pex9cX7GBpD5hB/sGv2+9f8hmxL6INPUkBQ8 Y/ATtoJYBa8CayexUxBDKgiRu55p5zW2PutocOggVshW8d+cHGwejnzY07GKnCt9DVf+ Iatixc34zRworTc/y2tvFWfqep5CQNkF4IopIq5kjtfVeUAa3mFX/wdNbYIJE6YjaBR5 NjQA6+BhHAA7qZMnQgfW2Lx5nu4Y5Fw3cu6fYVzgYCNDjE54+XUBN5dgrQHqgkGmya66 h+rg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@natalenko.name header.s=dkim-20170712 header.b=cpWxwtJK; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=natalenko.name Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f12si1153428eje.253.2019.11.20.23.15.12; Wed, 20 Nov 2019 23:15:36 -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=@natalenko.name header.s=dkim-20170712 header.b=cpWxwtJK; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=natalenko.name Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727022AbfKUHN3 (ORCPT + 99 others); Thu, 21 Nov 2019 02:13:29 -0500 Received: from vulcan.natalenko.name ([104.207.131.136]:48304 "EHLO vulcan.natalenko.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725842AbfKUHN3 (ORCPT ); Thu, 21 Nov 2019 02:13:29 -0500 Received: from mail.natalenko.name (vulcan.natalenko.name [IPv6:fe80::5400:ff:fe0c:dfa0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by vulcan.natalenko.name (Postfix) with ESMTPSA id 209EA63ABEF; Thu, 21 Nov 2019 08:13:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=natalenko.name; s=dkim-20170712; t=1574320407; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=xL3ut0Gb5LSFbLI5E9f4K9lAtbTVA7+YunIPYZDbV+o=; b=cpWxwtJKtqIoO/RqxCc67gYWTHufAnDGJ8CkT5onyhsNXZ+wg9KxLT1h2iLinv3poL3CUQ kRJz6nJoEkkg3IzuwGDTNfhhJ2kDHTJf0puhf1jZey7k02yJqJLyNpuUCGv35I+3i5C/Ro T9m2r7IV18VLQp9jvsYY+tYX4R+T+7I= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 21 Nov 2019 08:13:27 +0100 From: Oleksandr Natalenko To: linux-kernel@vger.kernel.org Cc: linux-block@vger.kernel.org, paolo.valente@linaro.org Subject: Injecting delays into block layer User-Agent: Roundcube Webmail/1.4.0 Message-ID: X-Sender: oleksandr@natalenko.name Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Paolo et al. I have a strong suspect that something is going wrong when the underlying block device responds with a large delay. What makes me thinking so is that I use a VM on some cloud provider, and they have substantial block device latency resulting in permanently high (~20%) iowait. It spikes occasionally when their cluster is overloaded, and when that happens, the I/O in my VM may stop and never recover. This is a rare occasion, but it really happens. What's worse, so far I've seen such a behaviour with BFQ only. I'm still testing other schedulers though. Important note: I have no strict evidences that this is *the* case, thus I'm asking for some suggestions. My idea is to fire up a local VM and inject delays to a block device while performing some I/O from within the VM. So the question is: how can those delays be injected? Using dm-delay? Can those delays be random? Thanks in advance. -- Oleksandr Natalenko (post-factum)