Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: Li Wang <liwang@linux.dev>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] mmapstress06: TCONF on systems without swap space
Date: Wed, 29 Apr 2026 08:10:43 +0200	[thread overview]
Message-ID: <20260429061043.GA539072@pevik> (raw)
In-Reply-To: <afFrf9OtAUkcOjLT@autotest-wegao.qe.prg2.suse.org>

> On Tue, Apr 28, 2026 at 06:34:15PM +0200, Petr Vorel wrote:
> > Hi all,

> > > Hi all,

> > > > mmapstress06 is designed to stress the mfile_swap kernel primitive, which
> > Uh, I overlooked "mfile_swap kernel primitive". Then the approach would make
> > sense, but is it really true? mfile_swap does not exist any more, not even in a
> > git log. Test was added in January 2003, e.g. even before 2.6.

> > > > manages shared anonymous memory. On architectures with large pages (like
> > > > 64KB on ppc64le), the test's hardcoded request for 32769 pages results
> > > > in a ~2GB mapping. So in suse test system configured with 2GB of RAM and
> > > > no swap space, the test will fails with following information:

> > I'm not really sure. if that's caused by missing swap or would it work on
> > machine with RAM big enough which has swap disabled (I guess you retest with
> > e.g. 8 GB RAM). Otherwise I'd prefer prefer to deal with errno ENOMEM (12)
> > instead (as I pointed out previously).


> Base description/implementation of test case, The original test is "passive," merely creating a 
> mapping and relying on external processes to trigger swapping(case has sleep_time parameter).
> Further more, this case is "ghost test" for current kernel, it do mmap but never 
> writes to it, so kernel never actually allocated memory, 
> Together with current obsolete logic(test targets legcy mfile_swap) i suggest just delete 
> it instead of wasting time patching(refactor) it. What do you think? @Petr @wang li?

I'm ok with deleting, but i hope others will have look on it as well.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-04-29  6:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 11:59 [LTP] [PATCH v1] mmapstress06: TCONF on systems without swap space Wei Gao via ltp
2026-04-27 12:26 ` Li Wang
2026-04-27 13:57   ` Wei Gao via ltp
2026-04-28  1:39     ` Li Wang
2026-04-27 13:57 ` [LTP] " linuxtestproject.agent
2026-04-28 11:52 ` [LTP] [PATCH v1] " Andrea Cervesato via ltp
2026-04-28 12:58 ` Petr Vorel
2026-04-28 16:34   ` Petr Vorel
2026-04-29  2:22     ` Wei Gao via ltp
2026-04-29  6:10       ` Petr Vorel [this message]
2026-04-30  8:01       ` Li Wang

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=20260429061043.GA539072@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@linux.dev \
    --cc=ltp@lists.linux.it \
    --cc=wegao@suse.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