Hi Peter,
Peter Teoh wrote:
Thank you Erik and James for the discussion.
On Tue, Nov 17, 2009 at 3:44 PM, Erik Nordmark <erik.nordm...@sun.com> wrote:
Peter Teoh wrote:
I see. My present h/w is AMD quad-core CPU, and two NIC, and one
zone (default) so far:
doing a mdb -k:
::squeue
ADDR STATE CPU FIRST LAST WORKER
ffffff02d7cbdac0 00320 0 0000000000000000 0000000000000000 ffffff0010818c60
ffffff02d7cbdb80 00320 2 0000000000000000 0000000000000000 ffffff00107eec60
ffffff02d7cbdc40 00820 3 0000000000000000 0000000000000000 ffffff000fa03c60
ffffff02d7cbdd00 00820 2 0000000000000000 0000000000000000 ffffff000f9a3c60
ffffff02d7cbddc0 00820 1 0000000000000000 0000000000000000 ffffff000f92dc60
ffffff02d7cbde80 00820 0 0000000000000000 0000000000000000 ffffff000f579c60
ffffff02d7cbde80::whatis
ffffff02d7cbde80 is ffffff02d7cbde80+0, allocated from squeue_cache
ffffff02d7cbddc0::whatis
ffffff02d7cbddc0 is ffffff02d7cbddc0+0, allocated from squeue_cache
note sure what the above data structures correspond to? squeues?
but it does not mapped to per-CPUs concept?
Yes. The output of ::squeue is showing a condensed version of the different
squeue_t on your system. To see the complete output, try:
::walk squeue_cache | ::print -a -t squeue_t
similarly for this:
::netstack
ADDR STACKID FLAGS
ffffff02d2ca0a40 0 000000
ffffff02d2ca0a40::whatis
ffffff02d2ca0a40 is ffffff02d2ca0a40+0, allocated from kmem_alloc_256
perhaps there is only one zone so far?
Again, to see everything, try:
::walk netstack | ::print -a -t netstack_t
Sorry about this question....so for each VNIC u will have one IP
instance, which is one netstack, correct?
Set up a vnic and run the above mdb commands and see.
Regards,
max
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
