Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp5768732ioo; Wed, 1 Jun 2022 12:10:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxDQRtRNsuuc5Y8SQNmADMI9F0Ap3KADiVefeW43faVnM2Qsmrfltfl0ofY43DZzsC22ptY X-Received: by 2002:a05:6a00:1826:b0:518:4c8b:c5db with SMTP id y38-20020a056a00182600b005184c8bc5dbmr1049972pfa.22.1654110602772; Wed, 01 Jun 2022 12:10:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654110602; cv=none; d=google.com; s=arc-20160816; b=UpOZi4b2RNJgzlumD4qmtimOICyakYrMPpZftjWHu4JRxuQa8Az3OgvdB9M46QNnmh +D+lfoSMIi/RRsuzmjaIhrbblDCqMPcSOi4fYJpUEd/w/f2J94veaeActOTk2aPcSLNU s2+QL6E0GPBrt9LBBajD4j3ieASfZRiuQM0AfOpPVm215W+U+rDpIdoawjHd60K6Ksrn +nQePmdVL1K9LgBFf+nJE1pgLsKA8bFoneixI99GE6uJZJtEx/CO9mnOGXJMiWQqB2eY +lAYag6FAp1IalB1tY2po8wdeV4S7YxgIVY9XwqCszSDiCBSFMunE2PjHHHR6CkDPRk/ JHLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :organization:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:dkim-signature; bh=qeG/Sta5uYqQzpYwCSHOVGWM8XywF0V7jsAoRO2ggsk=; b=08Z7c9idsxhHY2CxoCqJN6kLesOcRgNNzu8iwDjAjNJrLGH2UTkDQWY75nNSDz/dlP 2xYVm3yJuRytGVN1K8lvI5oZRDkepvDPLBNtGru+KzDUJut5Lh/r3qGEzylbcR9dxfLA 0hxUug407UOLZi1uZtuMo7ICTMsqRws3jnaxfiXBhBrrbQNIB/3jHuoLmahODqc7imrN Xg75rOvagx5kxxxovGos8MG88ChbJpJAbPb3UJ1DFjZZ/MRdWUB4+QIXGQZtarwCuXAe dckE7m/vROE4kmLkCfb5T+T1pKKSWQblX86SZBckPslFPLT0pswk7gyEFqmu+BTNDwcF 36Ng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=WNGmPGOi; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id q17-20020a656851000000b003fcbc8b5e7dsi1886342pgt.811.2022.06.01.12.10.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 01 Jun 2022 12:10:02 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=WNGmPGOi; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D9629125792; Wed, 1 Jun 2022 11:50:24 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347789AbiFAFYq (ORCPT + 99 others); Wed, 1 Jun 2022 01:24:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41484 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233773AbiFAFYp (ORCPT ); Wed, 1 Jun 2022 01:24:45 -0400 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 615CC9808E; Tue, 31 May 2022 22:24:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1654061084; x=1685597084; h=message-id:date:mime-version:subject:to:references:from: in-reply-to:content-transfer-encoding; bh=xQX06L/jjtHWDY6RNz/MSNPKBx6FjSI+BucvNOskFdQ=; b=WNGmPGOiy8HZnVKi5EgYf2dEGDICid/2pP52DOoxVHl3P71nH1C4qRqm zlxTAQ27/AoS5Et8lE2Pp2TlU9KXT/0bGyST10+v58VfzmY5adMY7KcQ+ Et6Qi5Xw71fHfr0LXzJsEypZQsY43I7aZlModN82LXavXpPxLlGh4uMoA o2UhyXCQEjH0pQqNn0x6kEvigrHPS78UxWahgoYJ1CqIT1dUvuJDaeC9e ILyzryrp8etSr0ufvoI5/GlgI+qfzddOPvBhR8VvhIGJolWShRlHzZI7a sycGHzU6kTUt3++60NCj8sgddAM8o9WzQFrXgEekKYY0yn9OVtD6bijGS g==; X-IronPort-AV: E=McAfee;i="6400,9594,10364"; a="275556165" X-IronPort-AV: E=Sophos;i="5.91,266,1647327600"; d="scan'208";a="275556165" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 May 2022 22:24:44 -0700 X-IronPort-AV: E=Sophos;i="5.91,266,1647327600"; d="scan'208";a="606070502" Received: from ahunter6-mobl1.ger.corp.intel.com (HELO [10.0.2.15]) ([10.252.44.223]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 May 2022 22:24:40 -0700 Message-ID: Date: Wed, 1 Jun 2022 08:24:36 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.9.1 Subject: Re: [PATCH] scsi: ufs: add a quirk to disable FUA support Content-Language: en-US To: Jaegeuk Kim , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, "Martin K . Petersen" , Bart Van Assche , Asutosh Das , Avri Altman , Bean Huo , Stanley Chu , Can Guo References: <20220531201053.3300018-1-jaegeuk@kernel.org> From: Adrian Hunter Organization: Intel Finland Oy, Registered Address: PL 281, 00181 Helsinki, Business Identity Code: 0357606 - 4, Domiciled in Helsinki In-Reply-To: <20220531201053.3300018-1-jaegeuk@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 31/05/22 23:10, Jaegeuk Kim wrote: > UFS stack shows very low performance of FUA comparing to write and cache_flush. > Let's add a quirk to adjust it. > > E.g., average latency according to the chunk size of write > > Write(us/KB) 4 64 256 1024 2048 > FUA 873.792 754.604 995.624 1011.67 1067.99 > CACHE_FLUSH 824.703 712.98 800.307 1019.5 1037.37 Wouldn't it depend on how much data might be in the cache? Do you have real-world use-cases where the difference is measurable? > > Signed-off-by: Jaegeuk Kim > --- > drivers/scsi/ufs/ufshcd.c | 3 +++ > drivers/scsi/ufs/ufshcd.h | 5 +++++ > 2 files changed, 8 insertions(+) > > diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c > index 3f9caafa91bf..811f3467879c 100644 > --- a/drivers/scsi/ufs/ufshcd.c > +++ b/drivers/scsi/ufs/ufshcd.c > @@ -5035,6 +5035,9 @@ static int ufshcd_slave_configure(struct scsi_device *sdev) > */ > sdev->silence_suspend = 1; > > + if (hba->quirks & UFSHCD_QUIRK_BROKEN_FUA) > + sdev->broken_fua = 1; > + > ufshcd_crypto_register(hba, q); > > return 0; > diff --git a/drivers/scsi/ufs/ufshcd.h b/drivers/scsi/ufs/ufshcd.h > index 94f545be183a..6c480c6741d6 100644 > --- a/drivers/scsi/ufs/ufshcd.h > +++ b/drivers/scsi/ufs/ufshcd.h > @@ -602,6 +602,11 @@ enum ufshcd_quirks { > * support physical host configuration. > */ > UFSHCD_QUIRK_SKIP_PH_CONFIGURATION = 1 << 16, > + > + /* > + * This quirk disables FUA support. > + */ > + UFSHCD_QUIRK_BROKEN_FUA = 1 << 17, Wouldn't it be more appropriate to make it a UFS_DEVICE_QUIRK_ since it presumably depends on the UFS device not the host controller? Also, as already commented by others, there needs to be a user of the quirk > }; > > enum ufshcd_caps {