Received: by oss.sgi.com id ; Mon, 26 Jun 2000 06:07:17 -0700 Received: from gst.gst.com ([208.219.159.150]:7689 "EHLO gst.gst.com") by oss.sgi.com with ESMTP id ; Mon, 26 Jun 2000 06:06:52 -0700 Received: from x0.org ([208.219.159.214]) by gst.gst.com (8.8.8/8.8.8) with ESMTP id JAA10666 for ; Mon, 26 Jun 2000 09:17:23 -0400 (EDT) Message-ID: <3957554C.D279FB5D@x0.org> Date: Mon, 26 Jun 2000 09:06:20 -0400 From: Andy X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.16 i586) X-Accept-Language: en MIME-Version: 1.0 To: "netdev@oss.sgi.com" Subject: [Fwd: Re: TCP, UDP,... Kernel modules] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-netdev@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;netdev-outgoing Content-Length: 812 Lines: 20 > How would it be helpful to make TCP a seperate module? I always > understood TCP as an integral part of functioning IP support. It seems > that it would be easier to just make the IP modular seeing as it is rather > small. My IPv6 module is 133k and I don't see how IPv4 could be much if > at all bigger (basic support). > > For the project I am working, it would be cool if TCP would be a kernel > > module (separate from IP). > > Is that possible? > > What other mess would this drag with? > > Did anybody work in this direction yet? Well, what if you do not need TCP/IP in boot time? Or maybe you need IP, but you do not need TCP. Think about the project of putting linux kernel into a bios. You want to eliminate as much as possible. I guess that's why they made IDE as a kernel module too. Andy