From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A9B3FC76188 for ; Tue, 16 Jul 2019 12:05:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 88A2A21721 for ; Tue, 16 Jul 2019 12:05:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732817AbfGPMFu (ORCPT ); Tue, 16 Jul 2019 08:05:50 -0400 Received: from verein.lst.de ([213.95.11.211]:41167 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728137AbfGPMFu (ORCPT ); Tue, 16 Jul 2019 08:05:50 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id B9E3E227A81; Tue, 16 Jul 2019 14:05:47 +0200 (CEST) Date: Tue, 16 Jul 2019 14:05:47 +0200 From: Christoph Hellwig To: Benjamin Herrenschmidt Cc: Christoph Hellwig , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, Jens Axboe , Keith Busch , Paul Pawlowski Subject: Re: [PATCH 2/3] nvme: Retrieve the required IO queue entry size from the controller Message-ID: <20190716120547.GA2388@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 16, 2019 at 08:58:28PM +1000, Benjamin Herrenschmidt wrote: > 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. Given that the spec currently requires bits 0 to 3 of SQES to be 6 we might as well not check SQES and just hardcode it to 6 or 7 depending on the quirk. That actually was my initial idea, I just suggested using the SQES naming and indexing.