From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] swapping01: make test more robust
Date: Fri, 22 Jan 2021 08:36:40 +0100 [thread overview]
Message-ID: <YAqAiB3fQwVAKHFF@pevik> (raw)
In-Reply-To: <8735ytzbj4.fsf@oc8242746057.ibm.com>
Hi Alex,
> Hi Petr,
> Date: Fri, 22 Jan 2021 08:16:41 +0100
> Message-ID: <874kj9zbja.fsf@oc8242746057.ibm.com>
> X-Trend-IP-HD: ip=[9.171.79.240]sender=(egorenar@linux.ibm.com)recipient=<ltp@lists.linux.it;liwang@redhat.com;pvorel@suse.cz>
> Petr Vorel <pvorel@suse.cz> writes:
> > Hi Alexander, Li,
> > First I found quite hard to have correct setup to avoid TCONF "Not enough swap
> > space to test". It often requires to add additional swap file via mkswap && swapon
> > and use some RAM with:
> > dd if=/dev/zero of=/dev/shm/fill bs=1k count=14024k
> > It'd be great if test could do required setup itself.
> > And it'd also help at least to print swap_free_init and mem_over_max in that TCONF:
> > if (swap_free_init < mem_over_max)
> > - tst_brk(TCONF, "Not enough swap space to test.");
> > + tst_brk(TCONF, "Not enough swap space to test (%ld < %ld)", swap_free_init, mem_over_max);
> yeah, that was a problem for me too when i was new to this test :/
:)
> > I tried to debug swapping01 on s390x (without this patch) with using additional
> > swap and eat RAM with dd. and got bus error (core dumped). Is that due too
> > aggressive memory eating? I'm not able to crash it on intel arch.
> that's something new for me. If possible please run it in gdb with debug symbols
> to find out where exactly this signal is raised.
I'll do.
Kind regards,
Petr
> Regards
> Alex
next prev parent reply other threads:[~2021-01-22 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 14:32 [LTP] [PATCH 1/1] swapping01: make test more robust Alexander Egorenkov
2021-01-18 10:50 ` Li Wang
2021-01-18 12:57 ` Li Wang
2021-01-18 14:04 ` Alexander Egorenkov
2021-01-20 7:25 ` Alexander Egorenkov
2021-01-20 12:46 ` Petr Vorel
2021-01-21 9:44 ` Li Wang
2021-01-22 6:40 ` Li Wang
2021-01-22 7:41 ` Petr Vorel
2021-01-22 7:56 ` Alexander Egorenkov
2021-01-24 4:32 ` Li Wang
2021-01-22 7:16 ` Alexander Egorenkov
2021-01-22 7:36 ` Petr Vorel [this message]
2021-01-21 9:30 ` 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=YAqAiB3fQwVAKHFF@pevik \
--to=pvorel@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.