All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tim Bird <tim.bird@am.sony.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: RFC: poky-tiny: init procedure
Date: Mon, 18 Jun 2012 12:50:05 +0100	[thread overview]
Message-ID: <1340020205.8481.15.camel@ted> (raw)
In-Reply-To: <4FDBA4B8.8000703@am.sony.com>

On Fri, 2012-06-15 at 14:10 -0700, Tim Bird wrote:
> One of our early efforts, getting busybox
> to not fork commands in init scripts that it had as
> builtins, proved to be a significant feature that is still
> valuable today to improve boot time.

I'd add that one thing we did with Poky's init system a while ago was
went through and for every fork we found, tried to find ways to avoid
it. Certainly, a few years ago, we were down to about four busybox/shell
util (grep/sed/cat) forks in the init scripts through to an X desktop.

I've not looked at this recently but we certainly used to be pretty good
in that area.

We also source init scripts, not execute them where they have the
extension .sh, again for performance (less exec overhead). This all
stayed pretty much compatible with sysvinit and is what we use to this
day. I appreciate we do need to improve, there is plenty of room for it
and look at things like systemd.

Cheers,

Richard




      parent reply	other threads:[~2012-06-18 11:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  0:33 RFC: poky-tiny: init procedure Darren Hart
2012-06-14  1:09 ` Tim Bird
2012-06-14  1:20   ` Darren Hart
2012-06-14  2:55     ` Darren Hart
2012-06-14  7:11 ` Tomas Frydrych
2012-06-14 21:09   ` Darren Hart
2012-06-15  6:31     ` Tomas Frydrych
2012-06-15  7:05       ` Thomas Petazzoni
2012-06-15 23:04         ` Darren Hart
2012-06-15 19:49       ` Tim Bird
2012-06-15 21:26         ` Tomas Frydrych
2012-06-15 23:15           ` Darren Hart
2012-06-16  8:53             ` Tomas Frydrych
2012-06-15 21:10   ` Tim Bird
2012-06-15 23:21     ` Darren Hart
2012-06-18 11:50     ` 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=1340020205.8481.15.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=tim.bird@am.sony.com \
    --cc=yocto@yoctoproject.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 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.