Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp697606ybi; Tue, 16 Jul 2019 03:59:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqzebQ/Dy1ySEjsKJt47KcXxbHl3aDzFpI7T01MfJSzLN3A1xGNxxhekKBQOMg2AalpfX+2m X-Received: by 2002:a65:6401:: with SMTP id a1mr32814984pgv.42.1563274796891; Tue, 16 Jul 2019 03:59:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563274796; cv=none; d=google.com; s=arc-20160816; b=O4dOMH2+BS04gpQPmyB1Y6zZV20I93rRZJlFYtqM8LitNvBAUH1Ztrf58xJObqPwUg q/3Yh8MQrg3ps/jJjGKyfwmY2j1L3PC4aQGYMucyU8SfqJtep0MnccMljDkR7+wNBQBv NIETV4x2451BcODvfnpBSB5KUUG13sip7FXVvik1GGwsIhco99jivv8IqNxk648pW5YD 4VZch4bL9Iz8CCSfU43WAl+RjyAoroI6W8pqx9QnF2KqWZ4Mi/EDI/n2SMyO5gOir4Bx ksYcxgwk6Izr9jtQ4eUa99gFJ3VdKnWuN+iA96hrknhdXX4zJfwpwAc99+43RKtgMSsB 1LdQ== 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; bh=HMaiDiAqxZZwiFSoiNdXxHxSk18VEGbC0xDQDQpLGyM=; b=J2js9ioUWzDa48iqpCrTOBOoCu7dfOjI21mFaZbfcKasH7IlegF4mkKN8Hx3TY2gld zEPAKCS7P0uxHND9jcmSnJO+//vbM5fX3LrlR/zmDopzR7s69rTpl/AVEIKaJbv0retZ osEabeJtjFHYLW6V202afKXBttMN7NMUVUGwqMBu37ib9woi3nqs1xATTUhwq0SdnXhM f+vTGwKMJs6jGPiIlF/Pqe1EQLh1+pM02N58j8Zaim0Su5aNN2Tqa0vNaoJ/1oWUVcY6 JXFad/whskegJUW13C+j0IYPYzUt1kP5pJvKaBPcqHUoVPw6xjeBIFAzZpeEp5AS3ggV nqbg== 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 n13si17654915plp.354.2019.07.16.03.59.40; Tue, 16 Jul 2019 03:59:56 -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 S2387494AbfGPK6p (ORCPT + 99 others); Tue, 16 Jul 2019 06:58:45 -0400 Received: from gate.crashing.org ([63.228.1.57]:53105 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733037AbfGPK6p (ORCPT ); Tue, 16 Jul 2019 06:58:45 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id x6GAwSFL022497; Tue, 16 Jul 2019 05:58:30 -0500 Message-ID: Subject: Re: [PATCH 2/3] nvme: Retrieve the required IO queue entry size from the controller From: Benjamin Herrenschmidt To: Christoph Hellwig Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, Jens Axboe , Keith Busch , Paul Pawlowski Date: Tue, 16 Jul 2019 20:58:28 +1000 In-Reply-To: <20190716093301.GA32562@lst.de> References: <20190716004649.17799-1-benh@kernel.crashing.org> <20190716004649.17799-2-benh@kernel.crashing.org> <20190716060430.GB29414@lst.de> <20190716093301.GA32562@lst.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-07-16 at 11:33 +0200, Christoph Hellwig wrote: > > > So back to the version > > > you circulated to me in private mail that just sets q->sqes and has a > > > comment that this is magic for The Apple controller. If/when we get > > > standardized large SQE support we'll need to discover that earlier or > > > do a disable/enable dance. Sorry for misleading you down this road and > > > creating the extra work. > > > > I think it's still ok, let me know... > > Ok, let's go with this series then unless the other maintainers have > objections. > > I'm still not sure if we want to queue this up for 5.3 (new hardware > enablement) or wait a bit, though. The main risk is if existing controllers return crap in SQES and we try to then use that crap. The rest should essentially be NOPs. Maybe I should add some kind of printk to warn in case we use/detect a non-standard size. That would help diagnosing issues. Cheers, Ben.