Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Sender: cgoldswo=codeaurora.org@mg.codeaurora.org
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date:   Fri, 09 Oct 2020 09:47:06 -0700
From:   Chris Goldsworthy <cgoldswo@codeaurora.org>
To:     tytso@mit.edu, adilger.kernel@dilger.ca,
        linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Question regarding ext4_journalled_aops: lack of migrate_page
In-Reply-To: <4296a311893a9173e6ba8b84a8ae16f4@codeaurora.org>
References: <4296a311893a9173e6ba8b84a8ae16f4@codeaurora.org>
Message-ID: <5c68c087a39752370f9f4bbea8b2e769@codeaurora.org>
User-Agent: Roundcube Webmail/1.3.9
Precedence: bulk

tOn 2020-10-08 23:42, Chris Goldsworthy wrote:
> Hi there,
> 
> ext4_aops and ext4_da_aops both have a migratepage callback, whereas
> ext4_journalled_aops lacks such a callback.  Why is this so?  I’m
> asking this due to the following: when a page containing EXT4 journal
> buffer heads ends up being migrated, fallback_migrate_page() is used,
> which eventually calls try_to_free_buffers(), which will call
> drop_buffers().  Drop buffers() can fail for a page if that page is on
> the LRU list (see
> https://elixir.bootlin.com/linux/v5.8.14/source/fs/buffer.c#L3225).
> Now, if buffer_migrate_page() was supplied as the migratepage callback
> for the journaled aops, this wouldn’t be problem since we ignore the
> LRU lists altogether.
> 
> Resolving this issue will benefit CMA allocations, which might have to
> migrate movable pages that were allocated from a CMA region (the
> assumption is that these pages can be migrated once the memory backing
> these pages is needed).
> 
> Thanks,
> 
> Chris.

An alternative solution to to placing in a migratepage callback is to 
actually remove the buffer heads from an LRU list in drop_buffers() - we 
tried upstreaming such a patch some time ago: 
https://lore.kernel.org/patchwork/patch/325406/ .  This would solve the 
problem, and would avoid having to get a migratepage callback for any 
other files systems that have aops without the callback.  This didn't 
get off the ground however, I'm picking up the line of questioning left 
in the previous thread, to determine why EXT4 doesn't have a migratepage 
callback.

Thanks,

Chris.

-- 
The Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora 
Forum,
a Linux Foundation Collaborative Project