All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] read_all: give more time to wait children finish read action
Date: Thu, 12 Apr 2018 11:01:26 +0800	[thread overview]
Message-ID: <CAEemH2ccG7grC2ObLOT-wDSp59v1b5W94cWnmY+VX1Mu+22KdQ@mail.gmail.com> (raw)
In-Reply-To: <87k1tevvld.fsf@rpws.prws.suse.cz>

Richard Palethorpe <rpalethorpe@suse.de> wrote:

>
> >  #define MAX_DISPLAY 40
> > +#define MICROSECOND 1
>
> Not necessary.
>
​
Ok.
​


> >
> >       for (i = 0; i < worker_count; i++) {
> > -             stop_attempts = 0xffff;
> >               if (workers[i].q) {
>
> Maybe change this to:
> if (!workers[i].q)
>    continue;
>
> To avoid a level of indentation.
>

​Sounds good.
​

> +                     tst_brk(TBROK,
> > +                             "Attempts %d times but still failed to
> push %s",
>                                  ^ Attempted
>

​Good catch.
​


>
> > +                             push_attempts, path);
> >               }
> >       }
> >  }
>
> Maybe you could put the "if (delaly < SECOND) ..." into a function?
>

​Firstly, I was thinking to take use of my new macros, but
consider that have not been reviewed. So I tend to keep
it as original, then replace them entirely after ltp gets
a generic loop functionality in library.



>
> Otherwise this looks good to me. There are some other things I want to
> change on this test, but we can leave those for another patch.
>

​Thanks, Patch v3 is coming...
​


-- 
Li Wang
liwang@redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20180412/49b93e3a/attachment-0001.html>

      reply	other threads:[~2018-04-12  3:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  9:47 [LTP] [PATCH v2] read_all: give more time to wait children finish read action Li Wang
2018-04-11 11:19 ` Richard Palethorpe
2018-04-12  3:01   ` Li Wang [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=CAEemH2ccG7grC2ObLOT-wDSp59v1b5W94cWnmY+VX1Mu+22KdQ@mail.gmail.com \
    --to=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 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.