Re: [RFC] reliability and scalability

[Greg KH <greg@kroah.com>]

On Sat, Feb 07, 2004 at 09:20:06PM +0100, Olaf Hering wrote:
>  On Sat, Feb 07, Greg KH wrote:
> 
> > On Sat, Feb 07, 2004 at 09:57:58AM +0100, Olaf Hering wrote:
> > >  On Sat, Feb 07, Chris Friesen wrote:
> > > 
> > > > Comments, anyone?
> > > 
> > > Better get rid of udevd and keep track of the latest add and remove
> > > SEQNUMs in the database.  unlink the devnodes and symlinks before
> > > creating new ones during add events.
> > 
> > And how would you re-order events in this situation?
> 
> What do you mean with reorder? Maybe I miss the point.

You have to order the events that come in by the seqnum, right?

So if you get a new one, you have to place it in the proper place amoung
all other outstanding events.

> Maybe something like this:
> 
> switch(action)
>         case add:
>                 if (last.add > seqnum)
>                         exit
>                 if (last.remove > seqnum)
>                         exit

exit?  Then do what?  Sit and spin?  You need something persistant to
stick around and figure out what to do next.

And udev is not big at _all_.  On my box it's the tiniest thing running
by a _large_ ammount:

$ size /sbin/udevd 
   text    data     bss     dec     hex filename
   5205      52      20    5277    149d /sbin/udevd

It's still smaller than /bin/true :)

$ size /bin/true 
   text    data     bss     dec     hex filename
   8623     724       0    9347    2483 /bin/true


thanks,

greg k-h


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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