linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevsynthesize as a udevstart+coldplug replacement
Date: Tue, 23 Aug 2005 20:09:17 +0000	[thread overview]
Message-ID: <430B826D.4050308@kolumbus.fi> (raw)
In-Reply-To: <20050823191542.GA29091@vrfy.org>

Kay Sievers wrote:

>On Tue, Aug 23, 2005 at 10:46:43PM +0300, Mika Penttilä wrote:
>  
>
>>Kay Sievers wrote:
>>
>>    
>>
>>>Here is "udevsynthesize" a possible replacement for the udevstart/coldplug
>>>combination we currently have. Usually very early in the boot process, it
>>>gets all available devices from sysfs and synthesizes the events these
>>>devices would have generated at creation time.
>>>The events are directly passed to the udevd daemom socket. udevd does all 
>>>the
>>>work and runs all the events asynchronously. udevsynthesize itself does
>>>not read any udev rule.
>>>
>>>It scans block and class devices to create the the device nodes for already
>>>available devices, which obsoletes the run of udevstart.
>>>After that, it scans for bus devices, which events may load modules or
>>>configure the device. If the bus type is known, the usual bus-specific
>>>values are added to the event environment.
>>>
>>>With the "rules-in-daemon" patch, the whole udevstart/coldplug handling
>>>(700 events) takes less than a second CPU time on a 1.7Ghz laptop.
>>>
>>>A typical boot script would do:
>>>prepare tmpfs on /dev
>>>create /dev/null
>>>start /sbin/udevd
>>>disable /proc/sys/kernel/hotplug (the input layer is still broken and 
>>>needs a kernel patch)
>>>run /sbin/udevsynthesize
>>>      
>>>
>
>  
>
>>What if udevd receives netlink messages and goes into "ignore unix 
>>socket" mode before/while synthesize?
>>    
>>
>
>No such mode exists. :) Only events with a SEQNUM set will possibly be
>ignored if received from userspace after netlink activity is detected.
>
>Kay
>
>  
>
Ok, there's the (seqnum != 0 && netlink active) test which keeps these 
messages passing through.

Thanks,
Mika




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-08-23 20:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 19:15 udevsynthesize as a udevstart+coldplug replacement Kay Sievers
2005-08-23 19:46 ` Mika Penttilä
2005-08-23 20:03 ` Kay Sievers
2005-08-23 20:09 ` Mika Penttilä [this message]
2005-08-23 20:47 ` Per Svennerbrandt
2005-08-24  3:50 ` Alexander E. Patrakov
2005-08-24  9:29 ` Marco d'Itri
2005-08-24  9:31 ` Marco d'Itri
2005-08-24 11:14 ` Olivier Blin
2005-08-24 19:37 ` Kay Sievers
2005-08-24 19:52 ` Olivier Blin
2005-08-24 20:05 ` Kay Sievers
2005-08-24 20:09 ` Kay Sievers
2005-08-24 20:18 ` Marco d'Itri
2005-08-24 20:18 ` Thierry Vignaud
2005-08-24 20:24 ` Kay Sievers
2005-08-24 20:27 ` Kay Sievers
2005-08-24 20:36 ` Kay Sievers
2005-08-24 20:40 ` Marco d'Itri
2005-08-24 20:42 ` Olivier Blin
2005-08-24 21:19 ` Thierry Vignaud
2005-08-25  6:43 ` Christian Zoz
2005-08-25  8:24 ` Marco d'Itri
2005-08-25 10:31 ` Christian Zoz
2005-08-25 10:36 ` Marco d'Itri
2005-08-25 18:20 ` Bill Nottingham
2005-08-25 18:33 ` Marco d'Itri

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=430B826D.4050308@kolumbus.fi \
    --to=mika.penttila@kolumbus.fi \
    --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).