[Netnice-kernels] netnice on linux
Status: Alpha
Brought to you by:
taost6
From: kartikey b. <kar...@ho...> - 2006-02-23 10:46:59
|
hi taka, Before I commit my further patches I'd like to ask you a few questions regarding netnice in particular and on linux. 1. Is it really necessary that we allow fine grain control over sockets too? I mean whether each individual socket should have its own association to vifs? What I am doing is rather than associating vifs to each socket , i am associating the vif to process only and the so_vifnet in socket is a pointer to the list of associated vifs of the process. And this way the system is more consistent. 2. I am enforcing that each process should have at least (and at most) one vif associated with the real net_device (ifnet in FreeBSD terminology). So a process cannot have more than "1" or less than "1" vif associated with eth0 at any given time. Whenever a process creates a vif, I am not allocating a new p_vifnet rather I am modifying the p_vifnet that is already associated with the vif that connects process to the real net_device (interface). When a process deletes the vif it simply reverts the p_vifnet to the vif that was associated with it before the creation of new vif. I know that these two approaches are not consistent with the way netnice is implemented on FreeBSD. However, they give a consistent view of the vif system. Any feedback? thanks --kartikey |