From: Marius Kittler <mkittler@suse.de>
To: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Fix memcontrol tests under Tumbleweed
Date: Thu, 12 Oct 2023 12:48:37 +0200 [thread overview]
Message-ID: <13368109.uLZWGnKmhe@linux-9lzf> (raw)
In-Reply-To: <ZSe6MNMQ6L5yJdV4@yuki>
Am Donnerstag, 12. Oktober 2023, 11:19:44 CEST schrieb Cyril Hrubis:
>
> Shouldn't we just remove all of dev_min_size records?
>
> We already have DEV_SIZE_MB set to 300 in lib/tst_device.c so with no
> limits we will use the default 300Mb.
I thought so, too. However, when running this particular test without this
minimum specified explicitly, it runs into the following error:
```
tst_test.c:1650: TINFO: === Testing on tmpfs ===
tst_test.c:1105: TINFO: Skipping mkfs for TMPFS filesystem
tst_test.c:1086: TINFO: Limiting tmpfs size to 32MB
tst_test.c:1119: TINFO: Mounting ltp-tmpfs to /tmp/LTP_memkrqX1e/mntdir
fstyp=tmpfs flags=0
memcontrol02.c:93: TPASS: Expect: (current=0) == 0
memcontrol02.c:99: TINFO: Added proc to memcg: memory.current=262144
memcontrol02.c:46: TPASS: Expect: (memory.current=52690944) >= (size=52428800)
memcontrol02.c:51: TPASS: Expect: (memory.stat.anon=52449280) > 0
memcontrol02.c:52: TPASS: Expect: (size=52428800) ~=
(memory.stat.anon=52449280)
memcontrol02.c:54: TPASS: Expect: (memory.current=52690944) ~=
(memory.stat.anon=52449280)
memcontrol02.c:93: TPASS: Expect: (current=0) == 0
memcontrol02.c:99: TINFO: Added proc to memcg: memory.current=262144
memcontrol02.c:69: TINFO: Created temp file: memory.current=262144
memcontrol_common.h:34: TBROK: write(9,0x7ffda0f93710,8192) failed: ENOSPC (28)
```
Judging by the 3rd TINFO message the size for tmpfs filesystems is
intentionally limited to 32MB which presumably also makes generally sense.
However, here we *really* need more space. This is most likely also the reason
why this test had `.dev_min_size = 256,` before in the first place. The other
tests don't need it, though (and I guess the `.dev_min_size = 256,` had just
been copied over from the first test).
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-12 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 13:45 [LTP] [PATCH v1] Fix memcontrol tests under Tumbleweed Marius Kittler
2023-10-12 9:19 ` Cyril Hrubis
2023-10-12 10:48 ` Marius Kittler [this message]
2023-10-26 9:57 ` Petr Vorel
2023-10-27 9:30 ` Cyril Hrubis
2023-10-27 10:34 ` Petr Vorel
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=13368109.uLZWGnKmhe@linux-9lzf \
--to=mkittler@suse.de \
--cc=ltp@lists.linux.it \
/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