Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2696416yba; Fri, 10 May 2019 17:07:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqwxXQw2UE4CKhvBSf6eFamWOXEBn/ifk40TJMa526uSoJn+ccBBD4BeZmDn23YmYNG8ENTm X-Received: by 2002:a65:49c7:: with SMTP id t7mr17081602pgs.324.1557533227056; Fri, 10 May 2019 17:07:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557533227; cv=none; d=google.com; s=arc-20160816; b=F3yLYkFSkNfibBa+qb3mGe/3q09j8kMfhKv/WzJ8eTQVaKLoMf8hfHhBcyHBj4RmA7 RJB/j4Ls64drPKWmELhMMIusAV9acEfYWXn4+u7DJ9DR2bYKab0F7Nq1HnIZqwpYygQA heXEHhjDL5dSm06JvB+Z7pQTouPGcf3TI0ZAGPkWT2/aE1O9BC9G+d7Z110YHrYNRGvt sNurl46hDkpOU89iauGPA+YmUJcDZFQSLX7iEk/7x15pKqAzRLXTieyz6bkxagQUuTy+ A+2wYTAwoQ0zKWIie03wv4jSs0vWo9KXAmY8iaRY7m/qzmwFxyGnKREuHSHZaH+/E7c+ Ch/w== 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:organization:from:references:cc:to:subject; bh=GpajMHPfq+e+4EBFDMcbaY5SZgkhT32AAql1Nc81rGU=; b=S389sqZ9LJDLautWAxawnOpYpU0Hs2I7w70HFAjSIpSsQ8Z1eVmSDwMp5Oh47YVUwD vhRNbyCdx0UwY/00HZGwT4OWGMuvsEBynPbWx4KEoAjMciQmmnOakfVRj4xCI47ujF/a YAkw+lheTCnNkBF3Is22+4R4OKUGTb+or8EklxDr8TNoID5HSmXuKesn/1PMFtVR8els 3iWICFKHI54CiFVbSH1NG8TRiwqG5zgNJxC3jZy6zNDt4vwQaqhmcriq+CPYJfDY/ZQG GpBWlLV+WZHr0IaEI67pSEjuAtQ3979IWF5/npLO770ZVPfZySYYMDd8SKPbgQjqHLWo xe1Q== ARC-Authentication-Results: i=1; mx.google.com; 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 j22si9363487pfi.167.2019.05.10.17.06.32; Fri, 10 May 2019 17:07:07 -0700 (PDT) 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; 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 S1728074AbfEKAFq (ORCPT + 99 others); Fri, 10 May 2019 20:05:46 -0400 Received: from mail02.iobjects.de ([188.40.134.68]:32782 "EHLO mail02.iobjects.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727921AbfEKAFq (ORCPT ); Fri, 10 May 2019 20:05:46 -0400 X-Greylist: delayed 459 seconds by postgrey-1.27 at vger.kernel.org; Fri, 10 May 2019 20:05:45 EDT Received: from tux.wizards.de (pD9EBF14A.dip0.t-ipconnect.de [217.235.241.74]) by mail02.iobjects.de (Postfix) with ESMTPSA id 0865E4168C0A; Sat, 11 May 2019 01:58:06 +0200 (CEST) Received: from [192.168.100.223] (ragnarok.applied-asynchrony.com [192.168.100.223]) by tux.wizards.de (Postfix) with ESMTP id 7A94E6D3233; Sat, 11 May 2019 01:58:05 +0200 (CEST) Subject: Re: [PATCH] bfq: backport: update internal depth state when queue depth changes To: Eric Wheeler , Sasha Levin Cc: Paolo Valente , Jens Axboe , "open list:BFQ I/O SCHEDULER" , open list , Eric Wheeler , stable@vger.kernel.org References: <1557510992-18506-1-git-send-email-stable@lists.ewheeler.net> <20190510201855.GB14410@sasha-vm> From: =?UTF-8?Q?Holger_Hoffst=c3=a4tte?= Organization: Applied Asynchrony, Inc. Message-ID: Date: Sat, 11 May 2019 01:58:05 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed 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 5/11/19 1:17 AM, Eric Wheeler wrote: > On Fri, 10 May 2019, Sasha Levin wrote: > >> On Fri, May 10, 2019 at 10:56:32AM -0700, Eric Wheeler wrote: >>> From: Jens Axboe >>> >>> commit 77f1e0a52d26242b6c2dba019f6ebebfb9ff701e upstream >>> >>> A previous commit moved the shallow depth and BFQ depth map calculations >>> to be done at init time, moving it outside of the hotter IO path. This >>> potentially causes hangs if the users changes the depth of the scheduler >>> map, by writing to the 'nr_requests' sysfs file for that device. >>> >>> Add a blk-mq-sched hook that allows blk-mq to inform the scheduler if >>> the depth changes, so that the scheduler can update its internal state. >>> >>> Signed-off-by: Eric Wheeler >>> Tested-by: Kai Krakow >>> Reported-by: Paolo Valente >>> Fixes: f0635b8a416e ("bfq: calculate shallow depths at init time") >>> Signed-off-by: Jens Axboe >>> Cc: stable@vger.kernel.org >> >> I wasn't clear on what was backported here, so I've queued the upstream >> version on 4.19 and 4.14, it doesn't seem to be relevant to older >> branches. > > > Thanks Sasha. We needed it for 4.19, I wasn't sure how far it would patch > back so I left the version off. BFQ was merged in 4.12 iirc, so if it > patched against 4.14, then 4.19 and 4.14 are the only ones that need it. It was applied in mainline for 5.1 and also applies fine to 5.0.x, so IMHO that wouldn't hurt either. thanks, Holger