Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp6683888ybl; Wed, 15 Jan 2020 08:32:58 -0800 (PST) X-Google-Smtp-Source: APXvYqwh+AWYcJquV46uWo/xs8x5frGo7LbXuTlySAV+963dRIEBrqLGQjFhjz4zLLncZFcqw+Sw X-Received: by 2002:aca:5f87:: with SMTP id t129mr533482oib.36.1579105978606; Wed, 15 Jan 2020 08:32:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579105978; cv=none; d=google.com; s=arc-20160816; b=tcl4UYqUirC/gGQHFJ4vUDolSq/3l1h1yzPlwrOV1PrJFxcaTq3cY8t03Pf2GzP3Jw POAvNv1ndZnvLOVzHhUd5c57oygAJ/308K60NU7vsjuCXCoXv4jQ6YbGKjtlP9Ggpt9H nA6TgZp3bp3c767FDkMRl6DnGSDcktuS6tNNf6iV+kHr9zM99jXzikVJyanaXwvc1t6h xQTzv5833ra2lWepdaamfFh5moPmucTByVzPIFIuoX3flBeCbxH37OvXzGdYYD2HAYR8 dEg2P/o8NjX2MHq5WM+o0I9YVr+2vGIkWwPrgyz8n32MEkJ0PnqMYX3yGKU5qTlZ/lnN M/hg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :reply-to:message-id:subject:cc:to:from:date; bh=WATReB3AFC/NmIYTi/o7rBb9ToMQqIwvnvv9ohMAl6w=; b=WK/cOSzNWlprHU7+kuNYwryv+HKxr/6iZm84uCHl1u0xMtvjzpLW60TWmg+rBb/heQ SSBW8/YcygHH9qIVsFz1uBrLkcVjRLKUEiu01LheZ2iWKfZXgxsb4UZ8lMWYWakK2H/F vslZyNPP7bG00RljQ62mZ0n7TniHG1U9jafHJ3zNR7nLlqmSDLZ9EJpIoju6xOra0rmh NiKVXBWHUCBZWk8Z7+aaAD/hwzhoPytJ0dsqANXY60f7GK8O5WbKAyoutPPIIsBOI4uc iBXGC+ekJHdyduc1eisjmijMYkVcQYLKcTjBZoxKG/6cl3Xb4Jt6tAu1wjIe/UNTj0F6 KKSA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q131si9082480oig.203.2020.01.15.08.32.45; Wed, 15 Jan 2020 08:32:58 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728901AbgAOQbo (ORCPT + 99 others); Wed, 15 Jan 2020 11:31:44 -0500 Received: from mx2.suse.de ([195.135.220.15]:39478 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726165AbgAOQbn (ORCPT ); Wed, 15 Jan 2020 11:31:43 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 0FC5BAB7F; Wed, 15 Jan 2020 16:31:41 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 43D81DA791; Wed, 15 Jan 2020 17:31:28 +0100 (CET) Date: Wed, 15 Jan 2020 17:31:28 +0100 From: David Sterba To: Kusanagi Kouichi Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] btrfs: Implement lazytime Message-ID: <20200115163128.GT3929@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Kusanagi Kouichi , linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org References: <20200114085325045.JFBE.12086.ppp.dion.ne.jp@dmta0008.auone-net.jp> <20200114212107.GM3929@twin.jikos.cz> <20200115134536820.LBFZ.46476.ppp.dion.ne.jp@dmta0009.auone-net.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200115134536820.LBFZ.46476.ppp.dion.ne.jp@dmta0009.auone-net.jp> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 15, 2020 at 10:45:36PM +0900, Kusanagi Kouichi wrote: > On 2020-01-14 22:21:07 +0100, David Sterba wrote: > > On Tue, Jan 14, 2020 at 05:53:24PM +0900, Kusanagi Kouichi wrote: > > > I tested with xfstests and lazytime didn't cause any new failures. > > > > The changelog should describe what the patch does (the 'why' part too, > > but this is obvious from the subject in this case). That fstests pass > > without new failures is nice but there should be a specific test for > > that or instructions in the changelog how to test. > > To test lazytime, I set the following variables: > TEST_FS_MOUNT_OPTS="-o lazytime,space_cache=v2" > MOUNT_OPTIONS="-o lazytime,space_cache=v2" How did you verify that the lazy time updates were applied properly?