Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp5321813ybi; Tue, 30 Jul 2019 18:35:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqwnCsS9W4J5e78SRdymIY6cFQnV4NxP4ULqa+g/Od2n+gQwPYU4Q5GHrwDYg0WxCy35ZN1E X-Received: by 2002:a17:902:8548:: with SMTP id d8mr118699890plo.100.1564536907538; Tue, 30 Jul 2019 18:35:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564536907; cv=none; d=google.com; s=arc-20160816; b=biCoiO6wtL0CWycJJ3OsTofWgYWCh3lybaAt7tLcW22oaJfOTeYGesoPuGHckBEiN5 aTEJjbtbBMCOKhv/nxrnWbpU+trmQLrbA+LzEutL5O4Y4XoPdWPxaU6YSGg4ojSxN7RH XaAKVFzv/By2vSP6W/qK3QgA55kdqblAf3lbuY2NXYOdgQDovW9wpjoNCPqOC13mlmQ0 mNdh9swjQPE04cyO0xgFGLpM/EymcegwDl9kDfti28PS5srODWcLdp43wJtwXyqctP1F DYun0PNNKD2K07h5uAwqJKzx4WjYc8Toh3Waxg60MasCUSs78PX+D2Qq10Qw9ZBRjYNb OFWQ== 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=KLSy7JLic0S0opodftR/K/CIXN940eQZqH1Vg2bDia4=; b=QF9OKE/uDVmOICo0Jkna0wW05MNNZBLqiojzXybpfcBRZfd38hzcdDuA/VXc4l6fTa hbpIZxUULQoNPvw4SBars4ukqPyyY+bL+NQ+UbTU1xOPSiodIiVYSbh1ni0qF6gIgJ5z arRFthvnIDwiHExQaCt4/LS5dy1rWePF9qRaXrSvZynZwv2fv1viScanU8I9b9WGsbWI i0aE1jCR5HUKC+k/VyUEH07ex7AZnQhcvMvbiotVOxJIqnXy2ZpFNkZbMmlBA/tg7SZT n8QpGx2bpy55sZSQIKG+h38KGrmwO5N4B0UJIzBzMKTkKD7dciO36qB8/GEkVHe2+VGr 08Ew== 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 j36si27984061plb.77.2019.07.30.18.34.52; Tue, 30 Jul 2019 18:35: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 S1728082AbfG3UPZ (ORCPT + 99 others); Tue, 30 Jul 2019 16:15:25 -0400 Received: from gate.crashing.org ([63.228.1.57]:33444 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727947AbfG3UPT (ORCPT ); Tue, 30 Jul 2019 16:15:19 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id x6UKF3aG026675; Tue, 30 Jul 2019 15:15:04 -0500 Message-ID: Subject: Re: [PATCH v3] nvme-pci: Support shared tags across queues for Apple 2018 controllers From: Benjamin Herrenschmidt To: Keith Busch Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, Paul Pawlowski , Jens Axboe , Christoph Hellwig , Minwoo Im , Damien Le Moal Date: Tue, 30 Jul 2019 13:15:03 -0700 In-Reply-To: <20190730153044.GA13948@localhost.localdomain> References: <20190730153044.GA13948@localhost.localdomain> 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-30 at 09:30 -0600, Keith Busch wrote: > On Fri, Jul 19, 2019 at 03:31:02PM +1000, Benjamin Herrenschmidt wrote: > > From 8dcba2ef5b1466b023b88b4eca463b30de78d9eb Mon Sep 17 00:00:00 2001 > > From: Benjamin Herrenschmidt > > Date: Fri, 19 Jul 2019 15:03:06 +1000 > > Subject: > > > > Another issue with the Apple T2 based 2018 controllers seem to be > > that they blow up (and shut the machine down) if there's a tag > > collision between the IO queue and the Admin queue. > > > > My suspicion is that they use our tags for their internal tracking > > and don't mix them with the queue id. They also seem to not like > > when tags go beyond the IO queue depth, ie 128 tags. > > > > This adds a quirk that marks tags 0..31 of the IO queue reserved > > > > Signed-off-by: Benjamin Herrenschmidt > > --- > > One problem is that we've an nvme parameter, io_queue_depth, that a user > could set to something less than 32, and then you won't be able to do > any IO. I'd recommend enforce the admin queue to QD1 for this device so > that you have more potential IO tags. Makes sense, I don't think we care much about the number of admin tags on these devices. I'm travelling, not sure I'll be able to respin & test before next week. Thanks. Cheers, Ben.