From: Chris Friesen <chris_friesen@sympatico.ca>
To: linux-hotplug@vger.kernel.org
Subject: [RFC] reliability and scalability
Date: Sat, 07 Feb 2004 08:01:29 +0000 [thread overview]
Message-ID: <40249B59.7080805@sympatico.ca> (raw)
I've got a couple more ideas for improving udevd, but before I go crazy
with this I wanted to get some opinions from people more experienced
than me.
First, how paranoid should we be about reliability? Right now there is a
(low) possibility of udevd crashing with unhandled messages on its rx
buffer, thus losing one or more hotplug events. Is this a problem?
Would people welcome a patch that closes the loop by sending an ack back
to udevsend?
Second, how many udev instances are we expecting to have outstanding at
a time? There are a couple of places in udevd (specifically the devpath
check and the udev_done code) that with the current data structures end
up being worst case ofO(n^2). Is this a problem? The average user will
never have an issue, but if we suddenly plug in a few thousand disks (a
number that's been mentioned before), is it a big deal if it takes a
bit longer to add them all? I see ways of getting around this, but
it may be overkill.
Comments, anyone?
Chris
-------------------------------------------------------
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
next reply other threads:[~2004-02-07 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 8:01 Chris Friesen [this message]
2004-02-07 8:57 ` [RFC] reliability and scalability Olaf Hering
2004-02-07 9:49 ` Kay Sievers
2004-02-07 19:30 ` Greg KH
2004-02-07 19:31 ` Greg KH
2004-02-07 20:20 ` Olaf Hering
2004-02-09 3:59 ` Kay Sievers
2004-02-21 1:01 ` 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=40249B59.7080805@sympatico.ca \
--to=chris_friesen@sympatico.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.