Received:  by oss.sgi.com id <S42401AbQFWW3L>;
	Fri, 23 Jun 2000 15:29:11 -0700
Received: from mail.inconnect.com ([209.140.64.7]:28610 "HELO
        mail.inconnect.com") by oss.sgi.com with SMTP id <S42400AbQFWW2z>;
	Fri, 23 Jun 2000 15:28:55 -0700
Received: (qmail 10170 invoked from network); 23 Jun 2000 22:28:55 -0000
Received: from ultra1.inconnect.com (209.140.64.2)
  by mail with SMTP; 23 Jun 2000 22:28:55 -0000
Date:   Fri, 23 Jun 2000 16:28:55 -0600 (MDT)
From:   Keyshaun <thekernel@subdimension.com>
X-Sender: kruger@ultra1.inconnect.com
To:     Andy <andy@x0.org>
cc:     netdev@oss.sgi.com
Subject: Re: TCP, UDP,... Kernel modules
In-Reply-To: <3952434A.94F4F9A5@x0.org>
Message-ID: <Pine.SOL.4.21.0006231623490.13165-100000@ultra1.inconnect.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-netdev@oss.sgi.com
Precedence: bulk
Return-Path: <owner-netdev@oss.sgi.com>
X-Orcpt: rfc822;netdev-outgoing

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).

Shaun
thekernel@subdimension.com

On Thu, 22 Jun 2000, Andy wrote:

> Hello!
> 
> 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?
> 
> 			Andy
>