Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754364AbeAGSMT (ORCPT + 1 other); Sun, 7 Jan 2018 13:12:19 -0500 Received: from [195.159.176.226] ([195.159.176.226]:36941 "EHLO blaine.gmane.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1754273AbeAGSMS (ORCPT ); Sun, 7 Jan 2018 13:12:18 -0500 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: Holger =?iso-8859-1?q?Hoffst=E4tte?= Subject: Re: [PATCH IMPROVEMENT] block, bfq: limit sectors served with interactive weight raising Date: Sun, 7 Jan 2018 18:09:47 +0000 (UTC) Lines: 15 Message-ID: References: <20171228111917.2767-1-paolo.valente@linaro.org> <5a9c6573-84a6-ae7b-7058-f202c7187065@applied-asynchrony.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Pan/0.142 (He slipped to Sam a double gin; 01b5bf4 git.gnome.org/pan2) Cc: linux-block@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Thu, 28 Dec 2017 15:00:56 +0100, Holger Hoffstätte wrote: > On 12/28/17 12:19, Paolo Valente wrote: > (snip half a tech report ;) > > So either this or the previous patch ("limit tags for writes and async I/O" > can lead to a hard, unrecoverable hang with heavy writes. Since I couldn't > log into the affected system anymore I couldn't get any stack traces, blk-mq > debug output etc. but there was nothing in dmesg/on the console, so it > wasn't a BUG/OOPS. So this turned out to be something else, sorry for the false alarm. -h