netdev
[Top] [All Lists]

Re: ipv4.o module

To: Dominic Duval <dd@xxxxxxxx>
Subject: Re: ipv4.o module
From: Matti Aarnio <matti.aarnio@xxxxxxxxxxx>
Date: Sat, 9 Mar 2002 16:41:31 +0200
Cc: netdev@xxxxxxxxxxx
In-reply-to: <3C89C85D.9070505@xxxxxxxx>; from dd@xxxxxxxx on Sat, Mar 09, 2002 at 03:31:25AM -0500
References: <3C89C85D.9070505@xxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Sat, Mar 09, 2002 at 03:31:25AM -0500, Dominic Duval wrote:
> Hi everyone,
> 
> I recently spent some time working on the "modularization" of the ipv4 
> stack. More precisely, this allows anyone to boot the kernel without any 
> ipv4 support (thus saving about 200k of RAM) and load a module 
> implementing the TCP/IP stack latter on.

  Excellent.  I had plan to do that latter this spring, but
  like always, there are parallel developments.

  One of my goals is to rip the TCP and UDP into separate submodules,
  so that we can in fact load in TCP, UDP and preferred IP (4 and/or 6)
  layers.

  You don't (yet) have 2.5.* diffs ?

      /Matti Aarnio

> The code is now at a stage where the ipv4.o module can be inserted and 
> removed at will, and it's actually quite stable (although it still needs 
> to be tested more heavily) . I know some people have shown some interest 
> for this feature in the past, so your feedback is appreaciated. The 
> patch is available for version 2.4.17 of the kernel, and can be 
> downloaded at the following location:
> 
> http://www-edu.gel.usherb.ca/duvd01/linux/diff-2.4.17-ipv4-0.11
> 
> Before anyone asks why ipv4 modularization is necesary: we are currently 
> making some heavy modifications to the TCP/IP stack for another project, 
> and modularizing the whole thing was the easiest way to optimize 
> development time, since the old "patch, compile, reboot, test" cycle is 
> now unnecessary with this patch.
> 
> Again, ideas/suggestions/comments are welcomed.
> 
> --
> Dominic Duval
> Étudiant, Génie Informatique
> Université de Sherbrooke
> 
> 

<Prev in Thread] Current Thread [Next in Thread>