From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6392847DF9B for ; Fri, 21 Aug 2026 14:32:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787322743; cv=none; b=GURqIfXotvSl9ofpRyj0Oy89b24pJVBU6GpIZzbFzTK7mtp2Bs1aKmi5TrvaPpcMS9KLwn7uxJlAl1F2kYSiPTb5iPTFNDC7rVS61zJjA1rdp5CoaL1xo8hzzkquQ8ec/fIJpD77E/cXWtEJ9+vY8tKQecGElFXC38Z19YuEmzs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787322743; c=relaxed/simple; bh=9jwIU2GlO/ZaxLhyAguupcdZzuqKlarz456wiIheIDw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=k0/pe8yzYmihwsTrLaT0awGZzApHT9oNrLptpN8GJhBTsO785ScV/Oeiyo7J67jEKCMNVibKhU9lyTz3AVxo3mp5a7Kdj7P70nFHUh+1uImXuA5Ewy3Cv741DyWQVueE+HTWOVLGsRdOjlhEVN7sfmQuvFvQG8Rn2nrwp96M8Qg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=R/zAraoZ; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="R/zAraoZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 03D561F000E9; Fri, 21 Aug 2026 14:32:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787322732; bh=+fMcDCG+5fbRAUA+2vA7F/VG/AR7ELvZw5ydJwkImkY=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=R/zAraoZilul6LBO2R+vPGHs16YxvywgycJazEwcRv/U5uwpz7TtJlL6WPdBA/IhZ QwuSjuW5JKlxa5zGkbaRgupG5GkcGGy3yaeTnV4GR8NjkXAtV+EX2DK43jK/mh0vhH AYYS4UJb6xlhJQ7Zy1hRqiG8EZMmNM+6zOWiqWUx3+Egb8IsuGLG9ptTtqMq2tBvZ1 CoxaNJdGSetk4CwGkrrp9+kfU3/7jSgpan7ho/iVU4VmyvUzina2PAppf9Z1lOsO5v c5bcdLgvjOWCt1WQDtiUc/4COtIAns094PRT1+SmkhbOcfvRjzwB+IeCE4nWHrFh8M kq+zfOgzCE53A== Date: Fri, 21 Aug 2026 22:32:03 +0800 From: Gao Xiang To: Jingbo Xu Cc: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] erofs: support large folio in inode_share mode Message-ID: Mail-Followup-To: Jingbo Xu , xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org References: <20260821112540.111105-1-jefflexu@linux.alibaba.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20260821112540.111105-1-jefflexu@linux.alibaba.com> On Fri, Aug 21, 2026 at 07:25:40PM +0800, Jingbo Xu wrote: > erofs_fill_inode() calls mapping_set_large_folios() on each erofs > file's own mapping, but in inode_share mode reads are routed to the > shared inode's page cache instead, whose mapping never had large > folio support enabled. > > Set up large folios for the shared inode's mapping as well. > > Signed-off-by: Jingbo Xu Reviewed-by: Gao Xiang Thanks, Gao Xiang