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=-1.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 D793DC2BA1A for ; Tue, 7 Apr 2020 02:59:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AC0882075E for ; Tue, 7 Apr 2020 02:59:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1586228355; bh=uCEYpsh9Jd3K0aQzSvHvZohM9flM5mt0gbSjnm7/fRo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=wzDVc90w9Eo3W0+Mj7nAJsV44vK2bOsQbq8Q2xnfRyFXqT4d6PSvO8VjUplyozDTl QdTWtPx/iZTHnnB34inclASZQXBCTr9pYRhdyPYCXoGKPf3A4l2ygBWK/qT2JfYNXU 6jIc4UkWjag6NyojKRLxxgOnKGuzoGbacBi7y+Og= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726628AbgDGC7O (ORCPT ); Mon, 6 Apr 2020 22:59:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:44926 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726303AbgDGC7O (ORCPT ); Mon, 6 Apr 2020 22:59:14 -0400 Received: from localhost (unknown [104.132.1.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7E9EB206B8; Tue, 7 Apr 2020 02:59:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1586228353; bh=uCEYpsh9Jd3K0aQzSvHvZohM9flM5mt0gbSjnm7/fRo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=F83BPuKRPnc+n9k++4IHrZRu3SWw4fwo5TjPh13e8iM/wXxKm5WFfFFFnnjkQFJau aFpwsHskvObGjROB/ii3oJuow/hRFM33NFCqiNkxnBy5ILTP/iFKw8isnzyS5Vrzwo CFyL86GW53bNQppJ7R0T0+KC+R0rKNAWnJJs9+qY= Date: Mon, 6 Apr 2020 19:59:13 -0700 From: Jaegeuk Kim To: Chao Yu Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com Subject: Re: [f2fs-dev] [PATCH] f2fs: introduce sysfs/data_io_flag to attach REQ_META/FUA Message-ID: <20200407025913.GB137081@google.com> References: <20200403161249.68385-1-jaegeuk@kernel.org> <0e627c29-7fb0-5bd6-c1d9-b96a94df62ae@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0e627c29-7fb0-5bd6-c1d9-b96a94df62ae@huawei.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/07, Chao Yu wrote: > On 2020/4/4 0:12, Jaegeuk Kim wrote: > > This patch introduces a way to attach REQ_META/FUA explicitly > > to all the data writes given temperature. > > > > -> attach REQ_FUA to Hot Data writes > > > > -> attach REQ_FUA to Hot|Warm Data writes > > > > -> attach REQ_FUA to Hot|Warm|Cold Data writes > > > > -> attach REQ_FUA to Hot|Warm|Cold Data writes as well as > > REQ_META to Hot Data writes > > Out of curiosity, what scenario it is used for? It's testing purpose to compare the bandwidths per different IO flags. > > Thanks,