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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1A13DC433FE for ; Thu, 20 Oct 2022 01:28:12 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A812C6B0074; Wed, 19 Oct 2022 21:28:11 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A09C46B0075; Wed, 19 Oct 2022 21:28:11 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 8AA896B0078; Wed, 19 Oct 2022 21:28:11 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id 779FF6B0074 for ; Wed, 19 Oct 2022 21:28:11 -0400 (EDT) Received: from smtpin08.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 534DD808C4 for ; Thu, 20 Oct 2022 01:28:11 +0000 (UTC) X-FDA: 80039591982.08.AA395AC Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) by imf17.hostedemail.com (Postfix) with ESMTP id DE60940030 for ; Thu, 20 Oct 2022 01:28:09 +0000 (UTC) Received: by mail-lf1-f47.google.com with SMTP id b2so31057855lfp.6 for ; Wed, 19 Oct 2022 18:28:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yJ87aDPEGTeaHnfrYNL1PdpyB4+D4BDv2/4OYt77PL8=; b=Y7IMT5Nava8658aIV/9QO13ByfJULYRCalDQklkwzr7W57i1tzFrfxO4BZxUSLNI1Q 0RsVQ2+++MTkLbnYW6UXTUaPVgUE0pLsrk2PU5O2S5tps/fuF9dInT+Ek5+TUoMmA2lM ksmOC76QO/P5imLzP6MDc22UAiZqlz2WOb7E347E2pwxgjrhHuh+849ikUlWkP24Kmf6 z5LRXnMuyZaGWMQ+T8YWo21W5HPV/nXuNidE4IzDt/OouGzE2dWIGPCSYeUeTAHs2I1I KWwSqOGe+tnckInL1M1FjJp9ZBfdygrcDWMKURef+V4FURVzPU5KgiSn3X8XyT9OEnJ2 KKpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=yJ87aDPEGTeaHnfrYNL1PdpyB4+D4BDv2/4OYt77PL8=; b=encTw9QTbJs65DcGoCeYkvidV3p++018xzZB+SOEZSVXb2FqRhWSjOo3q4paeoErjo QaL67p/uFF77VUlEuhAXGQYt4ZCGSth4LmQwQz55RuFWioxDpaby+ac+s904dbzSfAtf Zke3F1uBfaoBC9sYlEaSkarzYL0Z9Q+BJ45Sb/u17edN1BpKJh22hTghlEKF4w/x7h2b 61yGIX3PAG9ftIM1/JJObYKl76c9Awm3N5/mKDg/rYZ79XjQOo5GweK4pIkuftymxWLH 5G/MeuBYUKynlrcdteJk5neEdT1klcEybO2g2UGIuq3gtlsK/e7cLCtTSsskaxY6ZeFZ Hl5g== X-Gm-Message-State: ACrzQf1x02SSRjVZzTTCwtka+FdmUeC8rS3fakgjRpvRDd8Ns4bB8OF6 FyJ0a8DX2AIekBwkoBm5UB2O6HBH6rRd5TIOE1Q= X-Google-Smtp-Source: AMsMyM5lgPVYZzSz+ecmDAbZuQ5Xqy7gZatRR+i8Pveg+5vwjKrJ70pd22RAtoDevwIUmkPxwNNcyA3B8s5c2j/DYW4= X-Received: by 2002:a05:6512:158c:b0:4a2:5cf6:5338 with SMTP id bp12-20020a056512158c00b004a25cf65338mr3845266lfb.81.1666229288238; Wed, 19 Oct 2022 18:28:08 -0700 (PDT) MIME-Version: 1.0 References: <1665725448-31439-1-git-send-email-zhaoyang.huang@unisoc.com> <20221018223042.GJ2703033@dread.disaster.area> <20221019011636.GM2703033@dread.disaster.area> <20221019044734.GN2703033@dread.disaster.area> In-Reply-To: From: Zhaoyang Huang Date: Thu, 20 Oct 2022 09:27:39 +0800 Message-ID: Subject: Re: [RFC PATCH] mm: move xa forward when run across zombie page To: Matthew Wilcox Cc: Dave Chinner , "zhaoyang.huang" , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, ke.wang@unisoc.com, steve.kang@unisoc.com, baocong.liu@unisoc.com, linux-fsdevel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1666229290; a=rsa-sha256; cv=none; b=I+pT7AMQ/wvOGvzM7+zWUEMNDVhrUKCt7jOVpvD0Cf2Tp7kR4KZrh4ZMapfeM6maAg1lO3 D0HVQEvzvnT53bjDm5ujW46Futgl+sEdzePC0pE27V8USYnRuN/4g9852HKegOKoYa+b9e Tm8UuQfUkMEUQtT0sj/ObQPaFKAUEfw= ARC-Authentication-Results: i=1; imf17.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Y7IMT5Na; spf=pass (imf17.hostedemail.com: domain of huangzhaoyang@gmail.com designates 209.85.167.47 as permitted sender) smtp.mailfrom=huangzhaoyang@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1666229290; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=yJ87aDPEGTeaHnfrYNL1PdpyB4+D4BDv2/4OYt77PL8=; b=eNZdZ7WEQVugfsj5I4Uus0GacYDL6gbPJ03GQRLEa09ZF4dJSlI1UhAYynA3FHIN4HTmh+ U8FeEcuDjTorUmJFX6ybzne6Iuzx6yXjKHT9FG+mI2TciPcTKaipNtAqKQ7WeZVcskIIZH GUPy3n8ZTQFNasZts8So24aITUV0F7E= X-Stat-Signature: zfhb59t7uogzijy7gxyrrdncpzhuun41 X-Rspamd-Queue-Id: DE60940030 Authentication-Results: imf17.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Y7IMT5Na; spf=pass (imf17.hostedemail.com: domain of huangzhaoyang@gmail.com designates 209.85.167.47 as permitted sender) smtp.mailfrom=huangzhaoyang@gmail.com; dmarc=pass (policy=none) header.from=gmail.com X-Rspam-User: X-Rspamd-Server: rspam05 X-HE-Tag: 1666229289-91366 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000011, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, Oct 19, 2022 at 9:06 PM Matthew Wilcox wrote: > > On Wed, Oct 19, 2022 at 01:48:37PM +0800, Zhaoyang Huang wrote: > > On Wed, Oct 19, 2022 at 12:47 PM Dave Chinner wrote: > > > I removed the mapping_set_large_folios() calls in the XFS inode > > > instantiation and the test code has now run over 55,000 iterations > > > without failing. The most iterations I'd seen with large folios > > > enabled was about 7,000 - typically it would fail within 2-3,000 > > > iterations. > > hint from my side. The original problem I raised is under v5.15 where > > there is no folio yet. > > But 5.15 does use 2MB pages in shmem. You haven't really provided > any information, so I don't know whether the inode that you're having > problems with is a shmem inode. No, it is a f2fs inode using 4KB pages.