From: Scott James Remnant <scott@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Revisiting threaded udevd
Date: Sat, 27 Dec 2008 10:29:45 +0000 [thread overview]
Message-ID: <1230373785.7026.5.camel@quest> (raw)
In-Reply-To: <494F7942.6060702@tuffmail.co.uk>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Thu, 2008-12-25 at 17:36 +0000, Alan Jenkins wrote:
> Odd. I have started and I've not seen anything like this. Maybe
> you're
> doing something wrong. I don't have time to look at or try your patch
> today :-).
>
> libudev doesn't implement any locking itself. But AFAICS it's safe to
> use *different* libudev objects such as udev_devices from different
> threads. You generally don't need to modify the udev context object, so
> it seemed safe to share the context between threads (and just make sure
> to only call udev_ref/unref from a single thread).
>
I think I got it right, maybe I missed something that was in your
original patch?
The only vaguely unusual thing I was doing was running udevd in an
existing booted system, and running udevadm trigger on that - so there
would already have been udevdb entries for everything.
Scott
--
Scott James Remnant
scott@canonical.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-27 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 11:25 Revisiting threaded udevd Alan Jenkins
2008-12-24 11:37 ` Scott James Remnant
2008-12-25 17:36 ` Alan Jenkins
2008-12-27 10:29 ` Scott James Remnant [this message]
2008-12-27 19:07 ` Alan Jenkins
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=1230373785.7026.5.camel@quest \
--to=scott@canonical.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 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.