Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Niestroj <m.niestroj@grinn-global.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/systemd: Optionally disable hwdb
Date: Mon, 18 Apr 2016 10:25:46 +0200	[thread overview]
Message-ID: <57149A0A.6050401@grinn-global.com> (raw)
In-Reply-To: <20160415225321.0da4943f@gmx.net>

Hi,

On 15.04.2016 22:53, Peter Seiderer wrote:
> Hello Marcin Niestroj,
>
> On Fri, 15 Apr 2016 12:46:30 +0200, Marcin Niestroj <m.niestroj@grinn-global.com> wrote:
>
>> By default hwdb files are installed in /usr/lib/udev/hwdb.d
>> Currently they take about ~5MB. After first boot, systemd-hwdb tool
>> parses them and creates a binary in /etc/udev/hwdb.bin, which takes
>> another ~6.5MB.
>>
>> In case of initramfs images, hwdb parsing is done every boot. This adds
>> about 2-3 seconds to boot time in case of rootfs on SDHC class 10
>> card (benchmarked with am335x board). NAND boot takes even longer.
>>
>
> Perfect for this case would be 'systemd-hwdb update' run at built time to
> create the hwdb files once, but maybe stuff for a follow up patch...

I thought about it. This would propably require compiling part of 
systemd for the host PC, so the build time would be significally 
increased. This can be implemented if someone finds use case for it. For 
now it is ok for me that we totally disable hwdb and save additional 
space of the binary hwdb file.

For OpenEmbedded I saw a patch that was running QEMU to just generate 
the binary hwdb file at build time. I don't think this is an option for us.

-- 
Regards,
Marcin

  reply	other threads:[~2016-04-18  8:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 10:46 [Buildroot] [PATCH] package/systemd: Optionally disable hwdb Marcin Niestroj
2016-04-15 20:53 ` Peter Seiderer
2016-04-18  8:25   ` Marcin Niestroj [this message]
2016-06-07 14:37 ` Marcin Niestroj
2016-06-08 20:19 ` Yann E. MORIN
2016-06-13  9:20   ` Marcin Niestroj
2016-06-13 20:00     ` Yann E. MORIN
2016-06-15 21:19 ` Thomas Petazzoni

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=57149A0A.6050401@grinn-global.com \
    --to=m.niestroj@grinn-global.com \
    --cc=buildroot@busybox.net \
    /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