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 1E9A3C433F5 for ; Sat, 22 Jan 2022 18:21:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231812AbiAVSVJ (ORCPT ); Sat, 22 Jan 2022 13:21:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45544 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231531AbiAVSVI (ORCPT ); Sat, 22 Jan 2022 13:21:08 -0500 Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3BC9DC06173B for ; Sat, 22 Jan 2022 10:21:08 -0800 (PST) Received: by mail-pg1-x52e.google.com with SMTP id i8so11040650pgt.13 for ; Sat, 22 Jan 2022 10:21:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=LTkYoQuTiypETWTrbQ/dFwycrgwsW+MM4EvhuxglxJ8=; b=boGTkwI7uOpRKPl3/YAjA7Dczm2UHGuvpJ3PGDNqwf0QD3iIywDUp6HARwN2/RF09h C4Iqk82PYVyx3eWsFHg//uSCvC0BVNmmuFW+F8oNMCGrC26dQCfN70VHZd8Bg/IMOKg/ 6xRP2GyoSVK1AB/HlIyBn8rRVJmGoPNG34KY0A1OxMtnqqrb3wTaNvbmaQPQV7yGlFDR s2yaBrlwUypok6RzI5t6CPr3j7yBmTVNGU9Jq1yNpftgizmEoV2OvEt+BsRkejT8k4Nx QkItPamqYdAGHCROV6xS05yD/1gJ9xG9HP1s3+RftdPF98eccbI2+qnol66BNMEK507C HeQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=LTkYoQuTiypETWTrbQ/dFwycrgwsW+MM4EvhuxglxJ8=; b=OLEH4kFSHrZPaZStxCyJrcHRW4xsiQzWm9Bj+WY0ve6eb2PmtNYA8OoNV+4w+nZ0IP S58Q+bs/t66SFZ5cgmZO9ZFxzRWLy8Xu1lSaQPMuxnD9sCFBF35zzgkm3/0u+QUgvTqp Wym6VsKxczmrfSVlJzjkFAlNo2ce47y2Tu9GGW5bwZrKcppJcgBx/kmVdelxbWwpKENW J95jzrCnyqShzsugeH2OrIyLyj2JCYVfOBRBhyYYUTsGjz5ijLbxCICHHTCY0A01NRUy /DxfDCW+LMpxaMsyzSMQCFEf0q5CGxFEv3asA6DKvWF1ZS86x/yo/rcVxOVI6Pdb+xRz VNFA== X-Gm-Message-State: AOAM530koVIHaFMkjG3ilmvWbm3JnABCbBmI+uTmjDRF7ZdCYCQgM4An UdgOwdBy5ZUiFXtVT6Svq50XaFsgKZDKU1K1CNJ7oC1knGDx9A== X-Google-Smtp-Source: ABdhPJyhN/jhMZ7Sp0pITWvenWU61dtqwLoEhR3Y2Opj5FOh0V8sS6C8S2fnaMQ2n3DHmz6QeEtRHlLNrQi+YT/CoLY= X-Received: by 2002:a63:9712:: with SMTP id n18mr6687147pge.594.1642875667312; Sat, 22 Jan 2022 10:21:07 -0800 (PST) MIME-Version: 1.0 References: <7802ff58-d08b-76d4-fcc7-c5d15d798b3b@gmx.com> In-Reply-To: <7802ff58-d08b-76d4-fcc7-c5d15d798b3b@gmx.com> From: =?UTF-8?Q?Fran=C3=A7ois=2DXavier_Thomas?= Date: Sat, 22 Jan 2022 19:20:55 +0100 Message-ID: Subject: Re: Massive I/O usage from btrfs-cleaner after upgrading to 5.16 To: Qu Wenruo Cc: Filipe Manana , linux-btrfs , Qu Wenruo Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org > https://pastebin.com/raw/p87HX6AF The 7th patch doesn't seem to be having a noticeable improvement so far. > So even with more fixes, we may just end up with more IO for autodefrag, > purely because old code is not defragging as hard. That's unfortunate, but thanks for having looked into it, at least there's a known reason for the IO increase. Fran=C3=A7ois-Xavier