Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Jon Mason <jdmason@kudzu.us>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] oe_syslog.py: Handle syslogd/klogd restart race
Date: Fri, 21 Jun 2019 22:37:52 +0100	[thread overview]
Message-ID: <962677500f191acbfedbc026a5dd231155e2e744.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAPoiz9y+hqO5CNxxkL3XdpHMDJoEeF3LrGU_kFzhrhxiQacR-w@mail.gmail.com>

On Fri, 2019-06-21 at 15:26 -0400, Jon Mason wrote:
> On Fri, Jun 21, 2019 at 1:44 PM Jon Mason <jdmason@kudzu.us> wrote:
> > On Fri, Jun 21, 2019 at 12:58 PM <
> > richard.purdie@linuxfoundation.org> wrote:
> > > 
> > > I realise there is slightly more overhead but it might give us
> > > more
> > > chance of fixing all the races?
> > 
> > 4 extra function calls would almost be statistical noise.  I'll
> > code
> > it up to do the check every time regardless and add it for each
> > syslogd/klogd call.
> 
> A timed run of testimage on a Cortex A57x4 system (with KVM enabled)
> went from ~1m21s (1m23s, 1m22s,1m20s) to ~1m23s (1m22s, 1m25s,
> 1m24s).
> Without KVM enabled, it went from 20m6s to 20m56s. It's possible with
> a larger sample size that they would converge even more, but I think
> this is sufficient to show it's not a deal breaker to run it every
> time.

Sound good to me, thanks! :)

Cheers,

Richard



      reply	other threads:[~2019-06-21 21:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 15:42 [PATCH] oe_syslog.py: Handle syslogd/klogd restart race Jon Mason
2019-06-21 16:14 ` Richard Purdie
2019-06-21 16:39   ` Jon Mason
2019-06-21 16:58     ` richard.purdie
2019-06-21 17:44       ` Jon Mason
2019-06-21 19:26         ` Jon Mason
2019-06-21 21:37           ` richard.purdie [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=962677500f191acbfedbc026a5dd231155e2e744.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jdmason@kudzu.us \
    --cc=openembedded-core@lists.openembedded.org \
    /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