Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp747461ybh; Wed, 15 Jul 2020 14:13:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwpnBNhQ8zVJL43G+hdiTZHwG4woUsnuoz6SLhYwD58p9dMgse5uCsOkYJmg2mXULjs4jwI X-Received: by 2002:a17:906:a242:: with SMTP id bi2mr779206ejb.243.1594847621449; Wed, 15 Jul 2020 14:13:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594847621; cv=none; d=google.com; s=arc-20160816; b=z82EIKwc2w4IAElLLaUDCfaSXIuKj/cKqr63vlRwYFEhUR6zRPXkZWMbVuKrv3GcAu RvLmPfavrL2OGOhYtK49P9CNpNTAIlSLlhfKvAU8t4lCICZD2S37b3/eBoRYJTHNZEGw ZC/4qw94WtMGwnpdQSdqCL0V+2Ux41/j8hCe5Wt389NW5xZsxXIxyOZAfp31CpBIIOuZ S8SLG5UEx0xGzVILF1zm/QZPA04oFkO37BS0HHuS6fsZ9ToJq10LsChGqMPD8hLd2wi4 Xevhy2G7uuMXKR6P/WbWZc7RunkamvnBj+ICyDkzf5uR3SSJcWDFbMCVXY6rOlLuWU3r 8IpA== 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:dkim-signature :dkim-signature; bh=EhgG2CTQfcvprQjhPT7XeqhEzStobaQ7jP786fGmLKY=; b=n9PwyrUdIqME4A/lp9bXfWkV1XNlLzvkEi5QpY+X+/Ai5/hb+/eiNd7Zumk/WUdn6i tMuMU/cU/iMNhms4TDXMkIUdRmD7A6IyV7s4xxoUBpcRGmwt9JspU8nelqZks+qadNGV 0kEjRnxjrPnx6VDFjGu9keB3SxFt6nJG7pRGP4ZenLugU4l2ED0tcDk5Juk6fJsBa5me XHeacm+BZH15CzsjW5AF//fwui8fivnAgquXTBhATrKTW9AxgMX5SQFU6mrwmKv4Agjb 3hjGKvxb7YTt0IWcPpjH13iSAHCjeul6ArlkuDaGznX7sfYg/9Lt6+fM/Op2FLdNpyyX hUXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@octiron.net header.s=20180214 header.b="ecj/kQR7"; dkim=pass header.i=@octiron.net header.s=20180214 header.b=ylJXN1zV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=octiron.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 91si2351346edy.467.2020.07.15.14.13.18; Wed, 15 Jul 2020 14:13:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=fail header.i=@octiron.net header.s=20180214 header.b="ecj/kQR7"; dkim=pass header.i=@octiron.net header.s=20180214 header.b=ylJXN1zV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=octiron.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726770AbgGOVMz (ORCPT + 99 others); Wed, 15 Jul 2020 17:12:55 -0400 Received: from djelibeybi.uuid.uk ([45.91.101.70]:53750 "EHLO djelibeybi.uuid.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725917AbgGOVMz (ORCPT ); Wed, 15 Jul 2020 17:12:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=octiron.net ; s=20180214; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=EhgG2CTQfcvprQjhPT7XeqhEzStobaQ7jP786fGmLKY=; b=ecj/kQR7Z70erhemGvXu4P1wac FrdBrZo2hm4RJgYaWBumHD6y6PPBslakIDNWE1jBYowKPGzO2QvkY8xa3cDtcjo5ORYYokRW/4IRB PQyENqCxANS3GY7cyi3uO3CSAFO75oel29TJINAs55gKJNlXB0hkErgaRZwACcpRwTUkiT4MgaMxd 6K+ddxICXUOeNkRkqWA7zj0Hy1jPyuBr2ryTMK8waGoag3trr3PUpL/rcyq/7WcW74reRU08J8E2M TZcDfXnNWLNVPUUYL8lJz4SHE97VAh/gflLyQHZ9xLXg3bXThfmHRAfPp9JRXZbzMSIUhnxB1Rcc7 REwfLN9w==; Received: by djelibeybi.uuid.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jvohp-0005vV-Rx; Wed, 15 Jul 2020 22:12:52 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=octiron.net ; s=20180214; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=EhgG2CTQfcvprQjhPT7XeqhEzStobaQ7jP786fGmLKY=; b=ylJXN1zVTcXtEUvEGvkox9xu9i tyvpJWVYWnL8ErM+Bqe1FHnNZGBJaSpN3xUwnv7uMdmeSPzrfNl0nfTLXqX9wYKRlp4kX2PanCJb9 fWrqk4HxWdX+kR3fJPgUlKyEYlM7CUw6hfkGuhWwzdJUk1lL60FXatLkLzN5xvQSDvQuGymhsLL60 B7kO7/Xa8dWys2KB13+xnMXH46LTZ5ZCIrgX8g2R92TGrJXVJVZe0njteSqYQ9rGzUEUXSEM8FGpv bLsjD/utnPizQp6PU1vuPJSF7HDwLaisPDOB1lHVgGbB4g9rB0hjFWMtmQHC7aP0sOhOvv8nHDl3w qEw+mXcQ==; Received: by tsort.uuid.uk with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1jvohn-0008II-40; Wed, 15 Jul 2020 22:12:43 +0100 Subject: Re: [PATCH] ata: Disable queued TRIM for Samsung 860 SSDs To: "Martin K. Petersen" Cc: Jens Axboe , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, Park Ju Hyung , Tejun Heo References: <9324ef33-eedd-b965-37e8-b82e06778aab@0882a8b5-c6c3-11e9-b005-00805fc181fe> From: Simon Arlott Message-ID: <5059c002-2452-f427-76da-7b08a02748dc@0882a8b5-c6c3-11e9-b005-00805fc181fe> Date: Wed, 15 Jul 2020 22:12:43 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15/07/2020 21:53, Martin K. Petersen wrote: >> Despite the unsubstantiated claim from Samsung that "the improved >> queued trim enhances Linux compatibility" this does not appear to be >> true, even on Intel SATA controllers: > > I am aware of several people using 860 drives with queued TRIM. And I > haven't heard any complaints outside of the bug you referenced. > > Also, I have tested both 860 2.5" Pro and 860 mSATA EVO on a few > different systems in my lab without any problems. See: > > https://lore.kernel.org/stable/yq1h87du82d.fsf@oracle.com/T/ I've just checked and it happens on both my SATA 860s: 860 EVO 2TB (RVT04B6Q) on Intel Z170 860 PRO 1TB (RVM02B6Q) on Intel H170 > I really wish we had some more data to work with :( Is there a reliable way of reproducing this? I have a Marvell 88SE9235 that I could try with the EVO. > Lacking a proper heuristic I guess we don't have any choice to disable > the feature. But that's sad news for the people who currently don't have > problems since their performance will inevitably suffer. Samsung need to identify what the problem is before claiming that their Linux support is better, especially if specific chipsets are known to have issues... -- Simon Arlott