Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f41GWbq31792 for netdev-outgoing; Tue, 1 May 2001 09:32:37 -0700 Received: from vindaloo.ras.ucalgary.ca (vindaloo.ras.ucalgary.ca [136.159.55.21]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f41GWZM31778 for ; Tue, 1 May 2001 09:32:35 -0700 Received: (from rgooch@localhost) by vindaloo.ras.ucalgary.ca (8.10.0/8.10.0) id f41GW9U12212; Tue, 1 May 2001 10:32:09 -0600 Date: Tue, 1 May 2001 10:32:09 -0600 Message-Id: <200105011632.f41GW9U12212@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: BieshaarP@netscape.net (Peter Bieshaar) Cc: netdev@oss.sgi.com Subject: Re: possible suggestion for within the Linux kernel In-Reply-To: <17CEC8ED.094A580A.0225591B@netscape.net> References: <17CEC8ED.094A580A.0225591B@netscape.net> Sender: owner-netdev@oss.sgi.com Precedence: bulk [Please fix your MUA to wrap your lines at 72 characters] Peter Bieshaar writes: > I got this email address from Alan Cox. I think I have a really > great idea to implement into the Linux kernel. > But can actually not find any place to talk with anybody about > this. It is about tcp_doors, a door equivalent like Solaris > 2.51 > is using but then built onto the tcp layer. > > It will have great impact into a lot of OS stuff like mem mngmnt, > IPC, function, security, a lot of other exceptions and stack > management to name a few. I want to know what your ideas are and how > something like this should be set up. What's the benefit to having tcp_doors? Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca