All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3] memcg_stress_test.sh: ported to newlib
Date: Tue, 5 Feb 2019 00:34:35 +0100	[thread overview]
Message-ID: <20190204233435.GA14637@dell5510> (raw)
In-Reply-To: <c328de8d-418f-d81e-910a-890e6639af6c@arm.com>

Hi Cristian,

> Tested from you branch with ToT as:

> 10df48aa7 (HEAD -> pevik_ltp/christian/memcg_stress_test.sh.v3.fixes)
> memcg_stress_test.sh: fix memory usage
> ebd6efaa6 memcg_stress_test.sh: Further cleanup
> 02c520928 memcg_stress_test.sh: ported to newlib
> fc544f842 controllers/mem_process.c: Fix comparison warning
> ...

> on 4k/64k pages defocnfig....looks fine to me.

> Thanks a lot for the cleanup.
Thanks a lot for testing!
Pushed (with your Tested-by on my commit).

I did few cleanup changes in my commit (TINFO messages, fix missing local pid, redirect
stderr for wait to make it quiet, move TPASS message into run_stress()).

I wonder how to suppress kill message for the first cgroup pid:
/opt/ltp/testcases/bin/memcg_stress_test.sh: line 65: 14750 User defined signal 1   memcg_process_stress $mem_size $interval

This pid is the only one killed by -USR1, but line 65 is not in fist kill loop.
Therefore it cannot be killed by -KILL (second kill loop).

Kind regards,
Petr


  reply	other threads:[~2019-02-04 23:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 10:54 [LTP] [PATCH v3 0/1] memcg_stress newlib porting Cristian Marussi
2019-01-04 10:54 ` [LTP] [PATCH v3] memcg_stress_test.sh: ported to newlib Cristian Marussi
2019-01-28 16:32   ` Petr Vorel
2019-01-29 17:50     ` Petr Vorel
2019-01-29 19:25       ` Cristian Marussi
2019-02-01 13:45         ` Petr Vorel
2019-02-04 11:56           ` Cristian Marussi
2019-02-04 23:34             ` Petr Vorel [this message]
2019-02-05 17:46               ` Cristian Marussi
2019-02-14  8:32               ` Xiao Yang
2019-02-15 10:09                 ` Cristian Marussi

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=20190204233435.GA14637@dell5510 \
    --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.