> I am not driver programmer myself but i will be happy to start working > on network stack if someone can provide at least minimal working > driver for a 'classic' NIC that some virtual machine/emulator supports > :) > > Since PREX is microkernel OS there is another concern too: How will > the network stack be divided ? What separate process will be there ? > Is it ok to provide external 'routing' process (for ARP, IPv4, IPv6, > policy routing, etc) ? How we gonna deal with multiple routing tables > ? Will the firewall be separate process as well ? For example QNX uses > modified NetBSD 1.6 network stack and it is a single process. I don't > think this is a good idea. With correct design even performance should > not be a problem ... May be something like split networking in levels with netserver as a manager.
NetManager - Prex server Transport layer (TCPServ,UDPServ) Network layer (IP, ICMP, IPX) Link layer (Ethernet, ARP, PPP) Phys layer (drivers) Transport and network level is a one process, link and phys is another. Every process have API to communicate each other and prev\next level and internal "plugins". NetManager work at application level. It gets message for network, and send it to protocol level. Protocol server decides what protocol it will use and send message to "plugin" TCP. TCP returns it after some work, protocol server send result to IP "plugin", and then to next level. So complicated... :) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Prex-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/prex-devel
