From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Martin Schlemmer <azarah@nosferatu.za.org>,
linux-hotplug-devel@lists.sourceforge.net,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] udev 015 release
Date: Sat, 31 Jan 2004 04:17:18 +0100 [thread overview]
Message-ID: <20040131031718.GA21129@vrfy.org> (raw)
In-Reply-To: <20040129215529.GB9610@kroah.com>
On Thu, Jan 29, 2004 at 01:55:29PM -0800, Greg KH wrote:
> On Thu, Jan 29, 2004 at 06:52:05PM +0200, Martin Schlemmer wrote:
> > On Mon, 2004-01-26 at 23:50, Greg KH wrote:
> >
> > Is there a known issue that the daemon do not spawn?
>
> Hm, I don't know. This code is under major flux right now...
Hi Martin,
sorry, the code in the tree doesn't work.
I decided to try pthreads, cause I gave up with the I/O multiplexing,
forking and earning SIGCHLDS for manipulating the global lists.
The multithreaded udevd takes multiple events at the same time on a unix
domain socket, sorts it in a linked list and handles the timeouts if
events are missing.
It executes our current udev in the background and delays the execution
for events with the same DEVPATH. So we serialize the events only for
different devices.
I've posted the latest patch to the list a few minutes ago.
If you like, I'm happy to hear from your testing :)
If we decide not to stay with the threads model, cause klibc doesn't
support it now and ..., we at least have a working model to implement
in a different way.
thanks,
Kay
next prev parent reply other threads:[~2004-01-31 3:16 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 21:50 [ANNOUNCE] udev 015 release Greg KH
2004-01-26 22:15 ` Tomasz Torcz
2004-01-27 5:52 ` Chris Friesen
2004-01-27 22:22 ` Greg KH
2004-01-29 4:52 ` Martin Schlemmer
2004-01-29 21:54 ` Greg KH
2004-01-29 16:52 ` Martin Schlemmer
2004-01-29 21:55 ` Greg KH
2004-01-31 3:17 ` Kay Sievers [this message]
2004-01-31 17:54 ` Martin Schlemmer
2004-01-31 18:15 ` Kay Sievers
2004-01-31 18:27 ` Martin Schlemmer
2004-01-31 18:39 ` Kay Sievers
2004-01-31 18:47 ` Martin Schlemmer
2004-01-29 18:30 ` Martin Schlemmer
2004-01-30 4:41 ` Martin Schlemmer
2004-02-02 23:32 ` Greg KH
2004-02-03 4:12 ` Martin Schlemmer
2004-01-30 16:45 ` Prakash K. Cheemplavam
2004-01-30 17:23 ` Greg KH
2004-01-30 17:44 ` Prakash K. Cheemplavam
2004-01-30 17:49 ` Greg KH
2004-01-30 18:17 ` Prakash K. Cheemplavam
2004-02-01 15:24 ` Martin Schlemmer
2004-02-02 8:46 ` Prakash K. Cheemplavam
2004-01-30 17:33 ` Martin Schlemmer
2004-01-30 18:03 ` Andre Noll
2004-01-30 23:06 ` Tom Rini
2004-02-02 21:43 ` Greg KH
2004-02-05 0:31 ` [2.6 patch] remove USB_SCANNER Adrian Bunk
2004-02-05 1:14 ` Greg KH
2004-02-05 17:20 ` Azog
2004-02-05 17:30 ` Greg KH
2004-02-05 17:50 ` Stian Jordet
2004-02-05 17:57 ` Greg KH
2004-02-05 20:24 ` Leopold Gouverneur
2004-02-05 21:15 ` Stian Jordet
2004-02-05 21:36 ` Leopold Gouverneur
2004-02-06 1:15 ` Gene Heskett
2004-02-06 20:59 ` Bill Davidsen
2004-02-06 21:04 ` Greg KH
2004-02-01 22:52 ` hal daemon and ide-floppy J.A. Magallon
2004-02-02 3:16 ` Greg KH
2004-02-02 22:32 ` udev depends on /usr J.A. Magallon
2004-02-02 22:44 ` Greg KH
2004-02-02 23:01 ` J.A. Magallon
2004-02-03 4:10 ` Martin Schlemmer
2004-02-02 23:08 ` [ANNOUNCE] udev 015 release Prakash K. Cheemplavam
2004-02-02 23:11 ` Greg KH
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=20040131031718.GA21129@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=azarah@nosferatu.za.org \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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