Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3642146ybl; Tue, 21 Jan 2020 04:38:48 -0800 (PST) X-Google-Smtp-Source: APXvYqx4RNenXeyT6pVsfAsGPbMeaEw6pAwAHDl3/wMUcFFmsjmu2DV1tjCeZGlG/k2lXep8a8L8 X-Received: by 2002:aca:ab0e:: with SMTP id u14mr2837950oie.1.1579610328367; Tue, 21 Jan 2020 04:38:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579610328; cv=none; d=google.com; s=arc-20160816; b=N8/bo7iAA3CTuzRmG4HcGyc9FKdxZaANUYVZgyb/6D3lDBPJw85W0o2aE3PBYJkkEg JKGq6iltt5o6h2mDg+bG4fl2upGJqc1vpku6kyg1Goxk5PQxtCzK7CPV6R0WRjvDe+7r 6TR0sYqy49OjNneKb4bq5DgWxVDC6RtKb793qlHxPhT9VmPnSds7x3o3Y1QBRPSktpAR a8mxm5k3ywVj5FhnIhjooAYf6EQJxreKV3nFWVoXYvueXp+kMUYEwNjPhZurogoYwBkw YxG5VxhqbsvBZwNJ+Fofyf26GBWBMvd3BBzG1pYkb2RUgXkFQb5NSXIeI0eER99QCCW2 VngQ== 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:from:references:cc:to:subject; bh=p1k016ejqdDovADItqJ23vrdSn2JrlQOua6OXbc0BDc=; b=j25d/kabv22d7TT6WtFw2OYIuLTEqu1iPTY9Up3bE0pvzog5lxe2bPqKSp6M54Utms 7hSZYVgUnmWpwqSxoSDAhi9D5RY5+wqWZ8ss0kuP0nsqAeXFGNL1rYTbZPDNDuA1AGha 6+mkaQZkVzluQqhGqXjk3SLVdJyFiwr4XK7TyYM7Cw1iZjioqEedno7LmvFwzV8Qlf8o Hg6cGP0MD1KOQd2gX9hfkC2s00fAbJjEyzMPlvMi4wrcti0dHaxVNIxUhIY7pcNxlLZ6 JVF9aiC1gUEJQVg7Ew5wwCKOvCMBsX5Vb+mkTYzGfU9ctI7iGQENvXE4nZ9GqV/Kf99M hj4w== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=virtuozzo.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r12si21195520otq.156.2020.01.21.04.38.36; Tue, 21 Jan 2020 04:38:48 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=virtuozzo.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729541AbgAUMhm (ORCPT + 99 others); Tue, 21 Jan 2020 07:37:42 -0500 Received: from relay.sw.ru ([185.231.240.75]:33024 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727059AbgAUMhm (ORCPT ); Tue, 21 Jan 2020 07:37:42 -0500 Received: from dhcp-172-16-24-104.sw.ru ([172.16.24.104]) by relay.sw.ru with esmtp (Exim 4.92.3) (envelope-from ) id 1itsm0-0007Qx-N2; Tue, 21 Jan 2020 15:36:48 +0300 Subject: Re: [PATCH v4 6/7] dm: Directly disable max_allocate_sectors for now To: Mike Snitzer Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, martin.petersen@oracle.com, bob.liu@oracle.com, axboe@kernel.dk, agk@redhat.com, dm-devel@redhat.com, song@kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca, Chaitanya.Kulkarni@wdc.com, darrick.wong@oracle.com, ming.lei@redhat.com, osandov@fb.com, jthumshirn@suse.de, minwoo.im.dev@gmail.com, damien.lemoal@wdc.com, andrea.parri@amarulasolutions.com, hare@suse.com, tj@kernel.org, ajay.joshi@wdc.com, sagi@grimberg.me, dsterba@suse.com, bvanassche@acm.org, dhowells@redhat.com, asml.silence@gmail.com References: <157960325642.108120.13626623438131044304.stgit@localhost.localdomain> <157960337238.108120.18048939587162465175.stgit@localhost.localdomain> <20200121122458.GA9365@redhat.com> From: Kirill Tkhai Message-ID: Date: Tue, 21 Jan 2020 15:36:47 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <20200121122458.GA9365@redhat.com> 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 21.01.2020 15:24, Mike Snitzer wrote: > On Tue, Jan 21 2020 at 5:42am -0500, > Kirill Tkhai wrote: > >> Since dm inherits limits from underlining block devices, >> this patch directly disables max_allocate_sectors for dm >> till full allocation support is implemented. >> >> This prevents high-level primitives (generic_make_request_checks(), >> __blkdev_issue_write_zeroes(), ...) from sending REQ_ALLOCATE >> requests. >> >> Signed-off-by: Kirill Tkhai >> --- >> drivers/md/dm-table.c | 2 ++ >> drivers/md/md.h | 1 + >> 2 files changed, 3 insertions(+) > > You're mixing DM and MD changes in the same patch. > > But I'm wondering if it might be best to set this default for stacking > devices in blk_set_stacking_limits()? > > And then it is up to each stacking driver to override as needed. Hm. Sound like a good idea. This "lim->max_allocate_sectors = 0" in blk_set_stacking_limits() should work for dm's dm_calculate_queue_limits(), since it calls blk_stack_limits(), which is: t->max_allocate_sectors = min(t->max_allocate_sectors, b->max_allocate_sectors); Could you please tell is this fix is also enough for md? Kirill