From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/3] lib: add functions to adjust oom score
Date: Fri, 17 Dec 2021 09:25:56 +0100 [thread overview]
Message-ID: <YbxJlGOa59feuZH1@pevik> (raw)
In-Reply-To: <CAEemH2fpXYOADGY9PvcrfnXoGWrEjy+Lv6W2LxJGX--jN+u7LA@mail.gmail.com>
Hi Li,
> > BTW deliberately not documenting it as it should not be commonly
> Yes, actually it's not a commendatory API to users, and I think
> we do really avoid using it unless we have no better choice.
> (at least for OOM tests I can tell this)
> The main reason we use it is current kernel OOM is not very
> perfect, we just use it to help get the completed log for LTP.
Understand, thx for info.
> > used in tests? Also although oom_score_adj inheritance should be known to
> > person who will want to add it somewhere, I'd move it from commit message
> > to
> > source code (into header docs or or C API doc).
> Sounds reasonable, will add this in V2.
Thx!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2021-12-17 8:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 8:03 [LTP] [RFC] enable OOM protection for the library and test process? Li Wang
2021-12-13 9:32 ` Jan Stancek
2021-12-13 10:18 ` Li Wang
2021-12-13 15:08 ` Cyril Hrubis
2021-12-13 16:06 ` Martin Doucha
2021-12-13 16:15 ` Cyril Hrubis
2021-12-13 16:59 ` Martin Doucha
2021-12-14 6:46 ` Li Wang
2021-12-14 6:31 ` Li Wang
2021-12-16 3:41 ` [LTP] [PATCH 1/3] lib: add functions to adjust oom score Li Wang
2021-12-16 3:41 ` [LTP] [PATCH 2/3] ltp: enable OOM protection for main and test harness process Li Wang
2021-12-16 7:55 ` Petr Vorel
2021-12-16 9:50 ` Martin Doucha
2021-12-17 1:50 ` Li Wang
2021-12-16 3:41 ` [LTP] [PATCH 3/3] oom: enable OOM protection for mem lib process Li Wang
2021-12-16 7:57 ` Petr Vorel
2021-12-16 7:49 ` [LTP] [PATCH 1/3] lib: add functions to adjust oom score Petr Vorel
2021-12-17 2:02 ` Li Wang
2021-12-17 8:25 ` Petr Vorel [this message]
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=YbxJlGOa59feuZH1@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--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