linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: lsf-pc@lists.linux-foundation.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,
	jack@suse.cz, 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: [LSF/MM/BPF Topic] synthetic mm testing like page migration
Date: Thu, 27 Mar 2025 14:46:44 -0700	[thread overview]
Message-ID: <Z-XHRAgL0u2qO7LH@bombadil.infradead.org> (raw)
In-Reply-To: <Z-Rni3UhAF4RB7AY@dread.disaster.area>

On Thu, Mar 27, 2025 at 07:46:03AM +1100, Dave Chinner wrote:
> On Wed, Mar 26, 2025 at 11:59:48AM -0700, Luis Chamberlain wrote:
> > I'd like to propose this as a a BoF for MM.
> > 
> > We can find issues if we test them, but some bugs are hard to reproduce,
> > specially some mm bugs. How far are we willing to add knobs to help with
> > synthetic tests which which may not apply to numa for instance? An
> > example is the recent patch I just posted to force testing page
> > migration [0]. We can only run that test if we have a numa system, and a
> > lot of testing today runs on guests without numa. Would we be willing
> > to add a fake numa node to help with synthetic tests like page
> > migration?
> 
> Boot your test VMs with fake-numa=4, and now you have a 4 node
> system being tested even though it's not a real, physical numa
> machine.  I've been doing this for the best part of 15 years now
> with a couple of my larger test VMs explicitly to test NUMA
> interactions.

Suuuuweet! Given your long term use of it, we'll just make it a default
for all kdevops libvirt testing now!

> One of the eventual goals of check-parallel is to have all these
> things environmental variables like memory load, compaction, cpu
> hotplug, etc to be changing in the background whilst the tests
> running so that we can exercise all the filesystem functionality
> under changing MM and environmental conditions without having to
> code that into individual tests....

Indeed, I have high hopes for check-parallel.

  Luis

      reply	other threads:[~2025-03-27 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 18:59 [LSF/MM/BPF Topic] synthetic mm testing like page migration Luis Chamberlain
2025-03-26 20:46 ` Dave Chinner
2025-03-27 21:46   ` Luis Chamberlain [this message]

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-XHRAgL0u2qO7LH@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=apopple@nvidia.com \
    --cc=boris@bur.io \
    --cc=brauner@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=dave@stgolabs.net \
    --cc=david@fromorbit.com \
    --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=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).