linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] udevd - cleanup and better timeout handling
Date: Mon, 26 Jan 2004 19:11:10 +0000	[thread overview]
Message-ID: <20040126191110.GA10913@vrfy.org> (raw)
In-Reply-To: <20040125200314.GA8376@vrfy.org>

On Mon, Jan 26, 2004 at 10:22:34AM -0800, Greg KH wrote:
> On Sun, Jan 25, 2004 at 09:03:14PM +0100, Kay Sievers wrote:
> >   1. We are much too slow.
> >      We want to exec the  real udev in the background, but a 'remove'
> >      is much much faster than a 'add', so we have a problem.
> >      Question: is it neccessary to order events for different devpath's?
> >      If no, we may wait_pid() for the exec only if we have another udev
> >      working on the same devpath.
> 
> But how will we keep track of that?  It's probably easier just to wait
> for each one to finish, right?

We leave the message in the queue until we reach the SIGCHLD for this
pid. So we can search the queue if we are already working on this devpath,
and delay the new exec until the former exec comes back.

Is it feasible to run in parallel for different paths, or can you think
of any problem?

> >      We may want threads for this, but klibc doesn't support it.
> >      Nevermind, the ipc stuff is also not supported :)
> >      Any idea?
> 
> Heh, I can easily add the ipc stuff to klibc.
> I'm not a experienced enough userspace programmer to discuss the merits
> of either option here.  Anyone else?

IPC is from the 70's :) It's not refcounted so we may leave messages in the
kernel without any process using it. Sockets are nicer, we easily recognize,
if the daemon isn't running. But we need threads for this to implement it
without doing things like I/O multiplex or use of shared memory, cause
all tasks need to work on the same global queue.

So if we can get threads in klibc, I would prefer to switch to sockets.
IPC isn't really a  option for a todays program, but it works for us and
sockets don't solve any big problem we have.

thanks,
Kay


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-01-26 19:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 20:03 [patch] udevd - cleanup and better timeout handling Kay Sievers
2004-01-26 18:22 ` Greg KH
2004-01-26 19:11 ` Kay Sievers [this message]
2004-01-26 19:28 ` Greg KH
2004-01-26 19:42 ` Kay Sievers
2004-01-26 22:26 ` Greg KH
2004-01-26 22:56 ` Kay Sievers
2004-01-27  6:56 ` Kay Sievers
2004-01-27 18:55 ` Greg KH
2004-01-27 19:08 ` Kay Sievers
2004-01-27 19:13 ` Greg KH
2004-01-28 21:47 ` Kay Sievers
2004-01-29  1:52 ` Kay Sievers
2004-01-29  1:56 ` Kay Sievers
2004-01-29 15:55 ` Kay Sievers
2004-01-31  2:42 ` Kay Sievers
2004-02-01  9:08 ` Greg KH
2004-02-01 18:16 ` Kay Sievers
2004-02-02  2:19 ` Kay Sievers
2004-02-02  8:21 ` Greg KH
2004-02-02 11:50 ` Kay Sievers
2004-02-02 18:45 ` Greg KH
2004-02-02 21:36 ` Kay Sievers
2004-02-03  1:26 ` Greg KH
2004-02-03  6:43 ` Ling, Xiaofeng
2004-02-03 20:12 ` Kay Sievers
2004-02-04  0:56 ` Greg KH
2004-02-08  9:43 ` Olaf Hering
2004-02-08 15:22 ` Kay Sievers
2004-02-08 15:40 ` Olaf Hering
2004-02-08 15:57 ` Kay Sievers
2004-02-08 16:09 ` Olaf Hering

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=20040126191110.GA10913@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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).