From: Vasily Khoruzhick <anarsoul@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: udev problems on angstrom-2008.1
Date: Tue, 29 Sep 2009 09:11:15 +0300 [thread overview]
Message-ID: <200909290911.19203.anarsoul@gmail.com> (raw)
In-Reply-To: <20090929030152.GA7383@denix.org>
[-- Attachment #1: Type: Text/Plain, Size: 1303 bytes --]
В сообщении от 29 сентября 2009 06:01:52 автор Denys Dmytriyenko написал:
> Been there, done that.
> Short answer - you have too many requested devnodes for udev to handle
> within 32MB of RAM. If you absolutely need all the devices enabled in the
> kernel (try disabling/reducing LEGACY_PTY), consider replacing udev with
> mdev (or static devnodes). Or try moving udev's database from tmpfs into
> another partition, maybe on flash.
>
> Long answer - udev besides creating the actual devnodes also keeps its
> database in the same tmpfs filesystem. It consists of an internal directory
> structure with symlinks (a la sysfs) and is stored in /dev/.udev
> Keeping all that in tmpfs is not efficient, as it wastes inodes and
> apparently inodes in tmpfs/ramfs are the size of a memory page (4KB). By
> default tmpfs is limited to half the RAM, which in your case is 16MB. That
> would allow roughly 4000 inodes. You definitely need more, because of the
> above messages. Even if you fit all of them, using half of your available
> RAM just for udev is a total waste. So, consider suggestions above.
Oh, older versions of udev used to work here... I didn't expect it to take so
much RAM :)
Anyway, thanks for help.
Regards
Vasily
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2009-09-29 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 14:52 udev problems on angstrom-2008.1 Vasily Khoruzhick
2009-09-29 3:01 ` Denys Dmytriyenko
2009-09-29 6:11 ` Vasily Khoruzhick [this message]
2009-09-29 9:09 ` Phil Blundell
2009-09-29 18:10 ` Denys Dmytriyenko
2009-09-29 18:37 ` Vasily Khoruzhick
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=200909290911.19203.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=openembedded-devel@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 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.