From: Petr Vorel <pvorel@suse.cz>
To: Marius Kittler <mkittler@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Fix memcontrol tests under Tumbleweed
Date: Thu, 26 Oct 2023 11:57:24 +0200 [thread overview]
Message-ID: <20231026095724.GA585957@pevik> (raw)
In-Reply-To: <13368109.uLZWGnKmhe@linux-9lzf>
Hi Marius, Cyril,
> 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).
+1. Although it's unlikely we would really implement smaller loop device on
demand (nobody was really interested and 300 MB for a rootfs is not that much
nowadays), IMHO it's better to keep the real size request in case we really
implement it one day.
BTW more than 300 MB in the error message is 301 MB or more, right? I'm for 300
MB if it works (I suppose you have checked it), but XFS developers are wrong :).
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Thanks for handling this long standing issue (it looks like nobody runs
controllers on mainline :(.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-26 9:57 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
2023-10-26 9:57 ` Petr Vorel [this message]
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=20231026095724.GA585957@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mkittler@suse.de \
/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