[Top] [All Lists]

Re: ipv4.o module

To: Francois Romieu <romieu@xxxxxxxxxx>
Subject: Re: ipv4.o module
From: Matti Aarnio <matti.aarnio@xxxxxxxxxxx>
Date: Sun, 10 Mar 2002 01:17:31 +0200
Cc: Dominic Duval <dd@xxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <20020310000018.F18717@xxxxxxxxxxxxxxxxxxxxxxx>; from romieu@xxxxxxxxxx on Sun, Mar 10, 2002 at 12:00:18AM +0100
References: <3C89C85D.9070505@xxxxxxxx> <20020309164131.D10704@xxxxxxxxxxxxxxxxxxx> <3C8A7965.5010703@xxxxxxxx> <20020310000018.F18717@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Sun, Mar 10, 2002 at 12:00:18AM +0100, Francois Romieu wrote:
> Dominic Duval <dd@xxxxxxxx> :
> [...]
> > Sure, that would be the next logical steps. The current patch is more a 
> > proof of concept than anything else. For example, something better could 
> > be done with ipv6, in fact I'm not even sure how the ipv6 module (and 
> >  other sub-modules of ipv4) will react with all these modifications. I 
> On a related note, could somebody elaborate on why the EXPORT_SYMBOL 
> are done from net/netsyms.c ?

  Static linkage symbols of net-kind are done from there.
  It took some care year(s) ago to move ipv4 exports elsewere,
  when I did previous try at modularizing the IP stack.  Some
  remnants may be visible at:

> -- 
> Ueimor

/Matti Aarnio

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