From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] closing the loop -- retries and acks
Date: Sat, 21 Feb 2004 00:43:04 +0000 [thread overview]
Message-ID: <20040221004304.GE18146@kroah.com> (raw)
In-Reply-To: <403305A3.2070604@sympatico.ca>
On Wed, Feb 18, 2004 at 01:26:43AM -0500, Chris Friesen wrote:
> This patch reduces the already low chances of lost messages.
>
> Once udevsend successfully sends a message, it waits with a timeout for
> a response. If the response is good, then all is well, otherwise it
> sends the message again.
>
> In udevd, when we receive a request we store the address of the
> requestor, and then once the request has been handled we then send an
> ack back so that they know they have been taken care of.
>
> This patch takes care of the basics, but there are still a few things left:
> 1) tuning timeouts and retry numbers
Yeah, this is going to be the hardest in order to get this to work
"properly". What happens on a heavily loaded system? What would be the
proper timeout for that?
The idea is nice, but do we really need this? Has anyone ever lost a
hotplug message yet? I've tested a lot, under very high load and
haven't.
Any distros test udev out yet and feel that such a scheme is necessary
for them?
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
next prev parent reply other threads:[~2004-02-21 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 6:26 [PATCH] closing the loop -- retries and acks Chris Friesen
2004-02-18 8:27 ` Kay Sievers
2004-02-19 5:44 ` Chris Friesen
2004-02-19 7:52 ` Kay Sievers
2004-02-21 0:43 ` Greg KH [this message]
2004-02-21 0:44 ` Greg KH
2004-02-22 3:48 ` Chris Friesen
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=20040221004304.GE18146@kroah.com \
--to=greg@kroah.com \
--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).