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=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH autolearn=ham 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 7B530C04AB5 for ; Mon, 3 Jun 2019 15:15:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 44BEC24CF9 for ; Mon, 3 Jun 2019 15:15:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559574951; bh=54oATYsXXJ8P2M14fItKq+XktmeWUBPg/oIseVIgycE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:List-ID:From; b=aYCOmtEcNuyyuiu7+bbg15PGyydzcFgUeI7EhwoXWtxjrrs3o644Cyk3zX7RIV86S z4HvNLoVes1+izkVllTfU1uhsrHAb1+2flMqBBgtRD2SsgxJr2KtxuZVm3kHzYPdCH NSEQxaIqZmI1sqVBK3ciMXPGmK3OckLuBLtdMHig= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729345AbfFCPPu (ORCPT ); Mon, 3 Jun 2019 11:15:50 -0400 Received: from mail.kernel.org ([198.145.29.99]:57318 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729081AbfFCPPt (ORCPT ); Mon, 3 Jun 2019 11:15:49 -0400 Received: from [192.168.0.101] (unknown [58.212.135.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 296B524CF1; Mon, 3 Jun 2019 15:15:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559574949; bh=54oATYsXXJ8P2M14fItKq+XktmeWUBPg/oIseVIgycE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=TpgLbiVsdpdF49lOLEgS3pAq5qsVYM50r0Mf7QmMNRzjzT8t79qh6m4Fskm/t1uYo r1bBMKVQe/rmg2KBYIAKSwupUWc1XTvQ+PDNJhfTfzkQpaI1dEC/Plups1LVSK0PPR dZ1+o65toz9AvGiaT+4WjOIPD47zO+vVeIiX0Bc4= Subject: Re: [f2fs-dev] [PATCH v3 4/4] f2fs: Add option to limit required GC for checkpoint=disable To: Daniel Rosenberg , Jaegeuk Kim , Chao Yu , Jonathan Corbet , linux-f2fs-devel@lists.sourceforge.net Cc: linux-fsdevel@vger.kernel.org, kernel-team@android.com, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org References: <20190530004906.261170-1-drosen@google.com> <20190530004906.261170-5-drosen@google.com> From: Chao Yu Message-ID: Date: Mon, 3 Jun 2019 23:15:37 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20190530004906.261170-5-drosen@google.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-5-30 8:49, Daniel Rosenberg via Linux-f2fs-devel wrote: > This extends the checkpoint option to allow checkpoint=disable:%u[%] > This allows you to specify what how much of the disk you are willing > to lose access to while mounting with checkpoint=disable. If the amount > lost would be higher, the mount will return -EAGAIN. This can be given > as a percent of total space, or in blocks. > > Currently, we need to run garbage collection until the amount of holes > is smaller than the OVP space. With the new option, f2fs can mark > space as unusable up front instead of requiring garbage collection until > the number of holes is small enough. > > Signed-off-by: Daniel Rosenberg Reviewed-by: Chao Yu Thanks,