From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] closing the loop -- retries and acks
Date: Thu, 19 Feb 2004 07:52:55 +0000 [thread overview]
Message-ID: <1077177175.1129.16.camel@pim> (raw)
In-Reply-To: <403305A3.2070604@sympatico.ca>
On Thu, 2004-02-19 at 06:44, Chris Friesen wrote:
> Kay Sievers wrote:
> > On Wed, Feb 18, 2004 at 01:26:43AM -0500, Chris Friesen wrote:
> >
> >>This patch reduces the already low chances of lost messages.
>
> > It's sweet.
> > But isn't the case of handling a lost a message purely theroretical?
>
> Sure. But then, all error handling is theoretical.
>
I don't share this point. It's a question of econonmics all the time and
adding a transaction handling over a reliable communication for a case
with nearly no propabilty and all "critical" work somewhere else, sounds
really theroetical to me.
> > What problem we actually have is solved with this infrastructure?
> > A possibly crashing or exiting udevd in the time window from accepting
> > our message until its execution?
>
> Yes. Which could be up to 5 seconds if the sequence number is wrong.
>
> > Is the handling of this special case really needed?
>
> That's up to Greg, I guess.
>
> > Oh, and we don't handle a crashing udev :)
>
> We would if this patch was added...
>
> > We have a remaining risk all over the place and it seems that we try to
> > look better than the whole picture. We have failure paths with much
> > much higher propability.
> >
> > So, it's nice, sure.
> > But is it worth the extra complexity?
>
> That is indeed the question. It would be nice to lock down every
> possible problem, but I don't know if that's feasable.
>
Every possible problem? I don't think, that we should ever try that :)
thanks,
Kay
-------------------------------------------------------
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-19 7:52 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 [this message]
2004-02-21 0:43 ` Greg KH
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=1077177175.1129.16.camel@pim \
--to=kay.sievers@vrfy.org \
--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.