Date: Sun, 19 Sep 2004 14:00:34 +0200
From: Marc Ballarin <Ballarin.Marc@gmx.de>
To: "Ihar 'Philips' Filipau" <filia@softhome.net>
Cc: benh@kernel.crashing.org, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: udev is too slow creating devices
Message-Id: <20040919140034.2257b342.Ballarin.Marc@gmx.de>
In-Reply-To: <414D42F6.5010609@softhome.net>
References: <414C9003.9070707@softhome.net>
	<1095568704.6545.17.camel@gaston>
	<414D42F6.5010609@softhome.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1407
Lines: 36

On Sun, 19 Sep 2004 10:27:34 +0200
Ihar 'Philips' Filipau <filia@softhome.net> wrote:

>    Okay, okay. Let's spread delays and polling all over numerous init 
> scripts.

Just use /etc/dev.d. No delays, no polling. Everything is event based.

> 
>    You might be ten thousands time right. It is asynchronous process.
> 
>    But please listen to me: you are not going to handle that in _every_ 
> system application which deals with modules.

It  would not be necessary if the module provides some pseudo-device
without device nodes and loading will *always* succeed.
If this is not the case (ie. always), your script is even unsuitable for a
static /dev.
(I know that many scripts make that assumption, including my own.
Nevertheless it is wrong, and has always been wrong.)

> 
>    If there is problem, it doesn't mean we just pass it over. Probably 
> we need to solve it?

How do you want to solve it? We cannot look into the future, so how should
we know which device nodes "modprobe xyz" will or should create?
dev.d is a nice solution. If any device node is created, your script is
called. If it is the node you want, you perform your actions.

Regards
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/