From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Yongcheng Yang <yoyang@redhat.com>,
fstests@vger.kernel.org, smayhew@redhat.com, zlang@redhat.com,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] generic/551: prevent OOM on NFS on systems with no swap memory
Date: Wed, 25 Mar 2026 08:09:36 -0700 [thread overview]
Message-ID: <20260325150936.GE6212@frogsfrogsfrogs> (raw)
In-Reply-To: <acN4BV5QmtP2W_WK@infradead.org>
On Tue, Mar 24, 2026 at 10:52:05PM -0700, Christoph Hellwig wrote:
> On Wed, Mar 25, 2026 at 11:58:22AM +0800, Yongcheng Yang wrote:
> > From: Scott Mayhew <smayhew@redhat.com>
> >
> > We have frequently observed the oom-killer killing aio-dio-write-verify
> > when generic/551 is run on NFS filesystems on virtual machines in AWS.
> >
> > Virtual machines in AWS typically don't have a swap partition, so check
> > for that condition when testing NFS and only use 90% of available memory
> > when generating the list of write operations passed to
> > aio-dio-write-verify.
>
> I don't think this is a good idea. The proper fix is reduce whatever
> crazy large memory allocations this workloads causes in NFS. I suspect
> it might be page lists or similar, and just breaking them into somewhat
> smaller chunks and/or using potentially failing allocations to
> dynamically adjust would help.
I run fstests on XFS every night on a fleets of VMs with no swap and
never hit OOM.
Or at least I didn't until IT mandated CrowdStrike last week and now
it's anyone's guess if the test results are valid. <grumble>
--D
prev parent reply other threads:[~2026-03-25 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260325035854.2262636-1-yoyang@redhat.com>
2026-03-25 5:52 ` [PATCH] generic/551: prevent OOM on NFS on systems with no swap memory Christoph Hellwig
2026-03-25 15:09 ` Darrick J. Wong [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=20260325150936.GE6212@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.com \
--cc=yoyang@redhat.com \
--cc=zlang@redhat.com \
/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