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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2F665C433FE for ; Thu, 10 Mar 2022 14:25:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243477AbiCJO0V (ORCPT ); Thu, 10 Mar 2022 09:26:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58380 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243594AbiCJOZc (ORCPT ); Thu, 10 Mar 2022 09:25:32 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BAC1FB82D7; Thu, 10 Mar 2022 06:22:04 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 2E2F968AFE; Thu, 10 Mar 2022 15:21:48 +0100 (CET) Date: Thu, 10 Mar 2022 15:21:48 +0100 From: "hch@lst.de" To: "Luca Porzio (lporzio)" Cc: Manjong Lee , "david@fromorbit.com" , "axboe@kernel.dk" , "hch@lst.de" , "kbusch@kernel.org" , "linux-block@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "linux-nvme@lists.infradead.org" , "linux-raid@vger.kernel.org" , "sagi@grimberg.me" , "song@kernel.org" , "seunghwan.hyun@samsung.com" , "sookwan7.kim@samsung.com" , "nanich.lee@samsung.com" , "woosung2.lee@samsung.com" , "yt0928.kim@samsung.com" , "junho89.kim@samsung.com" , "jisoo2146.oh@samsung.com" Subject: Re: [EXT] Re: [PATCH 2/2] block: remove the per-bio/request write hint. Message-ID: <20220310142148.GA1069@lst.de> References: <20220306231727.GP3927073@dread.disaster.area> <20220309133119.6915-1-mj0123.lee@samsung.com> 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) Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Thu, Mar 10, 2022 at 11:34:40AM +0000, Luca Porzio (lporzio) wrote: > I work for Micron UFS team. I confirm and support Manjong message above. > There are UFS customers using custom write_hint in Android and due to the > "upstream first" policy from Google, if you remove write_hints in block device, > The Android ecosystem will suffer this lack. > > Can we revert back this decision? Or think of an alternative solution which > may work? Hell no. Given that these custmomers never gave a singe fuck to actually support whatever crap they came up with upstream we're not going to leave dead code to encurage them to keep doing this.