From: Bill Huey <billh@gnuppy.monkey.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH] C exceptions in kernel
Date: Sat, 23 Feb 2002 15:50:51 -0800 [thread overview]
Message-ID: <20020223235051.GA2412@gnuppy.monkey.org> (raw)
In-Reply-To: <200202231011.g1NABaU10984@devserv.devel.redhat.com> <25097.1014467212@ocs3.intra.ocs.com.au> <20020223075002.A23666@devserv.devel.redhat.com>
In-Reply-To: <20020223075002.A23666@devserv.devel.redhat.com>
On Sat, Feb 23, 2002 at 07:50:02AM -0500, Pete Zaitcev wrote:
> Personally, I have no problem handling current practices.
> But I may see the point of the guy with the try/catch patch.
> Do not make me to defend him though. I am trying to learn
> is those exceptions are actually helpful. BTW, we all know
> where they come from (all of Cutler's NT is written that way),
> but let it not cloud our judgement.
Uh, that's probably not right. If I've been told/remember correctly,
it's a technique that certain old school mainframe OSes use to
implement sophisticate fault recovery of various sorts. As you know,
one basically rewinds to the original point before the block is
called so that you can recover/continue from it.
It's not clear if an OS like Linux could really benefit from it since
everything that is so inheritently hotwired in the kernel, nor is it
clear how something like exceptions would conceptual map onto that
kind of system. Maybe DB/FS stuff would be a good of that stuff if
you have a condition that prevents a write to a disk (etc.l.) and
because they are data structure intensive systems.
But what about the TCP/IP stack ? or things in the bottom half ?
Those things are a bit more sticky and seem less compatible with
exceptions it seems.
bill
next prev parent reply other threads:[~2002-02-23 23:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 21:12 [RFC] [PATCH] C exceptions in kernel Dan Aloni
2002-02-22 21:28 ` Davide Libenzi
2002-02-22 22:10 ` Richard B. Johnson
2002-02-22 22:34 ` David B. Stevens
2002-02-22 22:48 ` Davide Libenzi
2002-02-23 3:37 ` Edgar Toernig
[not found] ` <mailman.1014437101.26721.linux-kernel2news@redhat.com>
2002-02-23 10:11 ` Pete Zaitcev
2002-02-23 12:26 ` Keith Owens
2002-02-23 12:50 ` Pete Zaitcev
2002-02-23 23:07 ` Jes Sorensen
2002-02-23 23:40 ` Keith Owens
2002-02-24 1:02 ` Jes Sorensen
2002-02-24 23:45 ` Richard Gooch
2002-02-23 23:50 ` Bill Huey [this message]
2002-02-24 1:31 ` Davide Libenzi
2002-02-24 2:55 ` Bill Huey
2002-02-23 15:13 ` Felix von Leitner
2002-02-23 15:21 ` bert hubert
2002-02-23 16:05 ` Dan Aloni
2002-02-23 16:22 ` Larry McVoy
2002-02-23 17:00 ` Dan Aloni
2002-02-23 17:52 ` Francois Romieu
2002-02-23 17:07 ` bert hubert
2002-02-23 17:47 ` Alexander Viro
2002-02-23 18:21 ` bert hubert
2002-02-23 18:31 ` Larry McVoy
2002-02-23 18:38 ` bert hubert
2002-02-23 19:12 ` Kurt Ferreira
2002-02-23 23:05 ` Jes Sorensen
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=20020223235051.GA2412@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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.