netdev
[Top] [All Lists]

Re: ipv4.o module

To: Chris Wedgwood <cw@xxxxxxxx>
Subject: Re: ipv4.o module
From: Matti Aarnio <matti.aarnio@xxxxxxxxxxx>
Date: Sun, 10 Mar 2002 04:26:03 +0200
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20020310002952.GA1325@xxxxxxxxxxxxx>; from cw@xxxxxxxx on Sat, Mar 09, 2002 at 04:29:52PM -0800
References: <3C89C85D.9070505@xxxxxxxx> <20020309164131.D10704@xxxxxxxxxxxxxxxxxxx> <20020310000434.GA1266@xxxxxxxxxxxxx> <20020310021111.G10704@xxxxxxxxxxxxxxxxxxx> <20020310002952.GA1325@xxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Sat, Mar 09, 2002 at 04:29:52PM -0800, Chris Wedgwood wrote:
> On Sun, Mar 10, 2002 at 02:11:11AM +0200, Matti Aarnio wrote:
> 
>       A pure IPv6 only system is the goal I had in mind.  The IPv6
>       does happen to need TCP and UDP, which even use shared port
>       number spaces (quite a complicated thing, actually.)
> 
> Ah, well then we need ipv4_core.o, ip_tcp_udp.o and ipv6_core.o sort
> of thing (you can't separate ICMP and ICMP6 from the core.o modules
> and the others depend on this).

  Something like that.

  I think there are things like timer management for tcp retransmissions,
  and such things which fall into "generic-ip" category, but there are
  also a lot of IPv4/IPv6 specific things.

  We can probably create a system where ipv4_core.o depends on  
  ip_tcp_udp.o, and same with ipv6_core.o.  However ipv6_core.o
  must not depend on  ipv4_core.o -- it does now.  Some hooks
  are called for so that _optional_ loading of ipv4 into the
  system, and integration with already loaded ipv6 is possible.

>   --cw

/Matti Aarnio

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