Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2013855ybl; Thu, 9 Jan 2020 05:32:35 -0800 (PST) X-Google-Smtp-Source: APXvYqyvGiZzwi8oOGJKfxZbEtPzQPMYvyB9vVlggZ8P5FulLWd4LXNeF+bYa/kDS1VhsgsIfW/Y X-Received: by 2002:a05:6830:155a:: with SMTP id l26mr8705687otp.339.1578576755296; Thu, 09 Jan 2020 05:32:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578576755; cv=none; d=google.com; s=arc-20160816; b=umvxEuARvH9LOpJST3eGqKNvvQCla3aGxgP19YvJSd7LtLfj3zQxW0eTPLReFupfC5 gbD/s9lTHxl34m19UPAIA1WTRhqOGmMIlhKpA4S41C4b9Uk4dgvLpnMNp5if31t+Xit1 aVsvQf6+Gd/McnIai28e6wL9JO3esIm1Vkx110Lr0YnyBixsoLY+QeQDEov4/vtFoloM Cmrc/DUt5XmVF2om/KwRXZjTi8ltWzSRm54+LrB/fnaQASqzhzE6Yu4+HS462LxqhnBV InEiHBl9xXfZEU9Z9efAp/WMKl9zJQ3xvsDLGvOQsxvgfSDifabkUMEZ5fhCnYS2ew+8 Kfhw== 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:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=to2tC83cIN6vDKqhn+LssLPUECktszP/zdsC8v7PRMA=; b=uZZYCVQImGoc2szSL1doRHUKfF/buy0XUuRNZk99OLIFz+cpwtpO9cUoMJR2fPsiKe PQ/k2jywZm5djNxML+tjR6J5FouNjYwJ0rDDatw3ol7sbe1/A82i4ZyU1Ol93V+vM+Vc k6keAvvN58Qkl24RKMdcA7JdAYfuwWKrA7SufNadFf7utyOp8rs40xS+pBvD6TTSq6zD gnFBxUpiyPqTXY3LaixwVvuKT5iydu1irEKxAeVDbd4RM4EemdtxzTldFFJvhQWsEOuR yO/sI7ApR5GELpcYypxDO1l5ARvR32Lhxc8wNAtfeXI8X+qVir4B5pHdSxj2Jdr74gSA Hy8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Z2mECv0S; 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=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w131si3471778oie.47.2020.01.09.05.32.23; Thu, 09 Jan 2020 05:32:35 -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=@redhat.com header.s=mimecast20190719 header.b=Z2mECv0S; 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=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730514AbgAINMi (ORCPT + 99 others); Thu, 9 Jan 2020 08:12:38 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:28963 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728974AbgAINMh (ORCPT ); Thu, 9 Jan 2020 08:12:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578575556; 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: in-reply-to:in-reply-to:references:references; bh=to2tC83cIN6vDKqhn+LssLPUECktszP/zdsC8v7PRMA=; b=Z2mECv0SnpxSKesECoVEIAXiW8xxHE/xu2WlxqAFTemsFxUsEy2vGkQIBDY9pEfuAFP2AI wNbl+KFVnPlsA1MzX3KuwKzwA8/WrgYrRtLrWKhazCfcnKGAANRwho0Wp/mFbyoO8wOJFL /8GSoluzlP3f8GuOt1LNJPaVi7q8enY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-222-XZIIqOGfNbKz-WjSOQcfLQ-1; Thu, 09 Jan 2020 08:12:33 -0500 X-MC-Unique: XZIIqOGfNbKz-WjSOQcfLQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 9DECC801E72; Thu, 9 Jan 2020 13:12:31 +0000 (UTC) Received: from emilne (unknown [10.18.25.205]) by smtp.corp.redhat.com (Postfix) with ESMTP id C10365C541; Thu, 9 Jan 2020 13:12:27 +0000 (UTC) Message-ID: Subject: Re: [resend v1 4/5] drivers/nvme/host/core.c: Convert to use disk_set_capacity From: "Ewan D. Milne" To: "Martin K. Petersen" , "hch@lst.de" Cc: "axboe@kernel.dk" , "Chaitanya.Kulkarni@wdc.com" , "mst@redhat.com" , "jejb@linux.ibm.com" , "linux-kernel@vger.kernel.org" , "linux-nvme@lists.infradead.org" , "linux-block@vger.kernel.org" , "Sangaraju, Someswarudu" , "Singh, Balbir" Date: Thu, 09 Jan 2020 08:12:27 -0500 In-Reply-To: References: <20200102075315.22652-1-sblbir@amazon.com> <20200102075315.22652-5-sblbir@amazon.com> <1b88bedc6d5435fa7154f3356fa3f1a3e6888ded.camel@amazon.com> <20200108150447.GC10975@lst.de> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2020-01-08 at 22:33 -0500, Martin K. Petersen wrote: > Christoph, > > > > The expected behaviour is not clear, but the functionality is not > > > broken, user space should be able to deal with a resize event where > > > the previous capacity == new capacity IMHO. > > > > I think it makes sense to not bother with a notification unless there > > is an actual change. > > I agree. > Yes, absolutely.