All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 4/4] syscalls/msgstress: tune limit of processes for small machines
Date: Thu, 19 Aug 2021 18:00:01 +0200	[thread overview]
Message-ID: <YR6AAfuxrdw9wuZ/@yuki> (raw)
In-Reply-To: <20210629121047.100391-5-krzysztof.kozlowski@canonical.com>

Hi!
> Forking the exactly amount of processes as the limit (either from
> max_pids or from cgroups) is risky - OS might be doing some work and
> interfere with the test.  Instead leave some reserve (hard-coded to
> 500) for the OS so the test won't fail on fork failure.

Isn't 500 far too many? I would expect that 50 would be more than
enough.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2021-08-19 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29 12:10 [LTP] [PATCH v4 0/4] syscalls/msgstress: fixes for small systems Krzysztof Kozlowski
2021-06-29 12:10 ` [LTP] [PATCH v4 1/4] include/tst_pid.h: fix language typo (subtraction) Krzysztof Kozlowski
2021-06-29 12:10 ` [LTP] [PATCH v4 2/4] tst_pid.c: fix fork failure on small memory systems Krzysztof Kozlowski
2021-06-29 12:10 ` [LTP] [PATCH v4 3/4] syscalls/msgstress03: " Krzysztof Kozlowski
2021-08-19 15:58   ` Cyril Hrubis
2021-08-19 16:02     ` Cyril Hrubis
2021-08-20  8:35       ` Krzysztof Kozlowski
2021-08-20 12:44         ` Cyril Hrubis
2021-08-20  8:35     ` Krzysztof Kozlowski
2021-06-29 12:10 ` [LTP] [PATCH v4 4/4] syscalls/msgstress: tune limit of processes for small machines Krzysztof Kozlowski
2021-08-19 16:00   ` Cyril Hrubis [this message]
2021-08-20  8:34     ` Krzysztof Kozlowski
2021-08-11 10:14 ` [LTP] [PATCH v4 0/4] syscalls/msgstress: fixes for small systems Krzysztof Kozlowski
2021-08-19 15:55   ` Cyril Hrubis

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=YR6AAfuxrdw9wuZ/@yuki \
    --to=chrubis@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.