Hi Mahesh, >> I have written a fix for the issue initially documented in 6696163, >> for which I >> have now opened 6817942 to get one bug for one issue. >> > Nils, I'll take a look at this and get back to you early next week.
Thank you. > Just for my understanding, whats the background/motivation in > your interest in increasing the max number of connections? My personal motivation is that I try to spread NFS load between a single Solaris NFS client and a single NFS Server (NetApp in this case, but that shouldn't matter) over several Gigabit Ethernet links. The main insight is that you need to spread NFS calls over several source IPs in order to achieve load balancing (Channeling/Trunking needs to balance by IP or source MAC, unless you do RR on Layer2, which will lead to out-of-order delivery and kill performance. Some implementations also allow to hash by TCP/UDP port, which also makes it necessary to spread NFS load over several connections). Another, similar motivation is documented in 6696163. If I understand correctly, the person who opened the bug initially observed that multiple TX ring capacity can not be exploited unless NFS load is spread over several connections. Nils
