All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH] mm: rewrite mtest01 with new API
Date: Fri, 1 Mar 2019 03:44:12 -0500 (EST)	[thread overview]
Message-ID: <269593361.3808924.1551429852336.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAEemH2cx0mPzhgAUKq01_4JXOnanQjK79JqEdPZ5N0kpO4A_QA@mail.gmail.com>




----- Original Message -----
> On Fri, Mar 1, 2019 at 4:03 PM Jan Stancek <jstancek@redhat.com> wrote:
> 
> Maybe give it few days, so other people can respond, if they like/don't like
> > going in this direction.
> >
> 
> Sure.
> 
> Btw, I'm not going to use shared memory here since that probably make
> things more complicated.
> I guess just do remaining time check in the parent while loop is enough for
> the two OOM situations
> which I was mentioned in last mail.
> 
> ==== mem_test() ======
>         ...
> 
> if (pid == 0)
> child_loop_alloc();
> 
> /* waits in the loop for all children finish allocating*/
> while(pid_count < pid_cntr) {
> if (tst_timeout_remaining() < 15)
> break;
> 
> sleep(1);
> }
> 
> if (dowrite) {
>                 pre_free - post_free check...

This doesn't look very accurate. Other system processes can influence this.

Do we need to check it at all? If a child didn't complete allocation
it's not going to signal parent.

> } else {
> ...
> }
> 
>        kill children here..
> 
> --
> Regards,
> Li Wang
> 

  reply	other threads:[~2019-03-01  8:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28  7:40 [LTP] [RFC PATCH] mm: rewrite mtest01 with new API Li Wang
2019-02-28 22:08 ` Jan Stancek
2019-03-01  6:05   ` Li Wang
2019-03-01  8:03     ` Jan Stancek
2019-03-01  8:26       ` Li Wang
2019-03-01  8:44         ` Jan Stancek [this message]
2019-03-05  7:04           ` 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=269593361.3808924.1551429852336.JavaMail.zimbra@redhat.com \
    --to=jstancek@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 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.