From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
patches@lists.linux.dev, fstests@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org, oliver.sang@intel.com,
hannes@cmpxchg.org, willy@infradead.org, apopple@nvidia.com,
brauner@kernel.org, hare@suse.de, oe-lkp@lists.linux.dev,
lkp@intel.com, john.g.garry@oracle.com, p.raghav@samsung.com,
da.gomez@samsung.com, dave@stgolabs.net, riel@surriel.com,
krisman@suse.de, boris@bur.io, jackmanb@google.com,
gost.dev@samsung.com
Subject: Re: [PATCH] generic/764: fsstress + migrate_pages() test
Date: Fri, 28 Mar 2025 07:22:45 +1100 [thread overview]
Message-ID: <Z-WzlUN6fSciApiC@dread.disaster.area> (raw)
In-Reply-To: <pociwdgfqbzw4mjass6u6wcnvmqlh3ddqzoeoiwiyqs64pl6yu@5ad7ne7rgwe2>
On Thu, Mar 27, 2025 at 12:53:30PM +0100, Jan Kara wrote:
> On Wed 26-03-25 11:50:55, Luis Chamberlain wrote:
> > 0-day reported a page migration kernel warning with folios which happen
> > to be buffer-heads [0]. I'm having a terribly hard time reproducing the bug
> > and so I wrote this test to force page migration filesystems.
> >
> > It turns out we have have no tests for page migration on fstests or ltp,
> > and its no surprise, other than compaction covered by generic/750 there
> > is no easy way to trigger page migration right now unless you have a
> > numa system.
> >
> > We should evaluate if we want to help stress test page migration
> > artificially by later implementing a way to do page migration on simple
> > systems to an artificial target.
> >
> > So far, this doesn't trigger any kernel splats, not even warnings for me.
> >
> > Reported-by: kernel test robot <oliver.sang@intel.com>
> > Link: https://lore.kernel.org/r/202503101536.27099c77-lkp@intel.com # [0]
> > Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
>
> So when I was testing page migration in the past MM guys advised me to use
> THP compaction as a way to trigger page migration. You can manually
> trigger compaction by:
>
> echo 1 >/proc/sys/vm/compact_memory
Right, that's what generic/750 does. IT runs fsstress and every 5
seconds runs memory compaction in the background.
> So you first mess with the page cache a bit to fragment memory and then
> call the above to try to compact it back...
Which is effectively what g/750 tries to exercise.
When it's run by check-parallel, compaction ends up doing a lot
more work over a much wider range of tests...
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2025-03-27 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 18:50 Luis Chamberlain
2025-03-26 21:10 ` Dave Chinner
2025-03-27 11:53 ` Jan Kara
2025-03-27 20:22 ` Dave Chinner [this message]
2025-03-27 21:35 ` Luis Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z-WzlUN6fSciApiC@dread.disaster.area \
--to=david@fromorbit.com \
--cc=apopple@nvidia.com \
--cc=boris@bur.io \
--cc=brauner@kernel.org \
--cc=da.gomez@samsung.com \
--cc=dave@stgolabs.net \
--cc=fstests@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=hannes@cmpxchg.org \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=jackmanb@google.com \
--cc=john.g.garry@oracle.com \
--cc=krisman@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mcgrof@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=p.raghav@samsung.com \
--cc=patches@lists.linux.dev \
--cc=riel@surriel.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox