thank you for discussion.... On Mon, Nov 16, 2009 at 2:59 AM, Erik Nordmark <erik.nordm...@sun.com>wrote:
> James Carlson wrote: > > An squeue belongs to exactly one netstack. A netstack may have one or >> many squeues. >> > > I don't think that is the case. In fact tcp.c has: > * This list is per squeue and squeues are shared across the tcp_stack_t's. > > The motivation is that the number of squeues should be related to the > number of CPUs to get good scalability, while the netstacks is a logical > construct for the exclusive-IP zones. Hence with 100 exclusive-IP zones it > doesn't make sense to have 100 squeues on a 8 CPU/core system. > > Erik > Yes, there is an entire file for all the netstack API here: http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/os/netstack.c#netstack_register and there is an ARC for this: http://arc.opensolaris.org/caselog/PSARC/2006/366/20060531_erik.nordmark (exclusive IP stack per zone). wow....each netstack for each IP zone? what is the purpose? at the kernel level, everyone can see and modify each other right? so I don't think it is for privilege segregation - in the security sense? sorry for the newbie question, i will read into these documentation.....slowly :-). -- Regards, Peter Teoh
_______________________________________________ networking-discuss mailing list networking-discuss@opensolaris.org
