[openbeosnetteam] mbuf.h
- From: "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>
- To: "OpenBeOS Networking" <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Mon, 22 Sep 2003 19:59:41 +0200
Hi,
why does mbuf.h define max_xxx variables like max_linkhdr? This creates the
following problems:
1. The ppp interface module does not link against libkernelppp.a because of
multiple definitions of max_linkhdr, etc.
2. Those variables are never assigned a value, though, the tcp and ipv4 modules
use them.
Where do their values come from?
Can tcp and ipv4 use them? Does this not result in undefined values for max_xxx?
If that is really a problem:
How can we solve that? Should I add a new function to the core module (as I
will add a control() function anyway) and define a new structure that will be
used to retrieve the values for those variables and can I remove the current
definitions from the header?
What about the other definitions like mbpool (or whatever they are called)?
Waldemar
- Follow-Ups:
- [openbeosnetteam] Re: mbuf.h
- From: Philippe Houdoin
Other related posts:
- » [openbeosnetteam] mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- » [openbeosnetteam] Re: mbuf.h
- [openbeosnetteam] Re: mbuf.h
- From: Philippe Houdoin