So basically L4 grants IO caps to the network card's io ports to whatever task acts as the network driver, and it's the driver task's job to bang on the card's I/O and hook up with whatever other tasks represent packet/protocol/whatever layers of the ISO 7 layer stack.


On Mon, Nov 2, 2015 at 5:48 PM, Tim Newsham <tim.newsham+sel4@gmail.com> wrote:
seL4 does not provide a network stack or even
network device drivers.  An OS on top of seL4
would have to provide their own drivers and stack
and is free to put them in a single server or in
different servers and choose how to communicate
between them.


On Mon, Nov 2, 2015 at 2:38 PM, Yuxin Ren <ryx@gwmail.gwu.edu> wrote:
Hi,

I have a few questions about network stack in sel4.

Is network stack implemented in the kernel or user level?
If in user level, are different protocols (IP/TCP) implemented in a
single server or different servers?
If in different servers, how do they communicate with each other?

Is there any example code to show how to use network? How to send and
receive TCP or UDP packets?
How can I set up the network environment on bare metal machine? Is
there documentation or instruction?

Thanks a lot!
Yuxin

_______________________________________________
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel


_______________________________________________
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel