From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: speed up udev-acl.mk
Date: Mon, 21 Dec 2009 15:32:01 +0000 [thread overview]
Message-ID: <20091221153201.GC2268@piware.de> (raw)
Hey Kay,
Kay Sievers [2009-12-21 16:25 +0100]:
> If it's only about the ACL stuff, we could change the udev-acl logic
> to maintain hidden symlinks in:
> /dev/.udev/acl/c116:32 -> ../../snd/controlC1
>
> then the udev-acl program would just need to apply the same ACL to all
> nodes found in this directory. :)
This would be one option.
I thought about providing a special-case implementation of
udev_enumerate_scan_devices() which fires when there is only a
property match and nothing else. In this case we could just walk
/dev/.udev/db (which we have to do anyway to match the properties) and
skip the /sys walk. This would speedup other applications as well
which search for tagged devices.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
next reply other threads:[~2009-12-21 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 15:32 Martin Pitt [this message]
2009-12-21 15:38 ` speed up udev-acl.mk Kay Sievers
2009-12-21 15:54 ` Martin Pitt
2009-12-21 16:10 ` Kay Sievers
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=20091221153201.GC2268@piware.de \
--to=martin.pitt@ubuntu.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).