Thanks, I have used your method to set the MTU to 8000, but big issues rise up (1) Ping with msgsize>1476 will not work. (2) Ping with msgsize<=1476 works, but the latency become longer. (3) Netperf testing can not be executed. Even if I kill the netperf process, status of socket created by netperf still remains "ESTABLIBSHED", I think "FIN" packet have not been sent out successfully by each other.
Thanks, Zhihui 2008/6/24, Paul Guo - SUN ERI - Beijing China <[EMAIL PROTECTED]>: > > You can set default_mtu in /kernel/drv/ixgbe.conf to enable jumbo frame. > Please remember to rem_drv/add_drv or update_drv to make it to become > effective. > Currently we are working on adding/enabling/tuning more features (such > as LSO/TSO, multiple > rings, etc) which will eventually increase the performance greatly. Stay > tuned. > > -Paul > > > Why the maximum MTU for ixgbe is only 1500, same to e1000g? > > With 1500 mtu, the maximum throughput using netperf for 10G network is > > less than 3Gbit/s > > > > > > 2008/6/23, Samuel Tu <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>: > > > > Glad to know it works. We're go on the development with more features > > supporting. The LSO supporting is coming. > > > > Thanks, > > Samuel > > > > zhihui Chen wrote: > > > > Thanks a lot. it works now and I can ping from this machine to > > another machine with another same-type adapter. We will make a > > detail perfomance testing in next few weeks. > > Zhihui > > > > > > 2008/6/23, zhihui Chen <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>>>: > > > > Thank Samuel. I have tried the "add_drv" command and each time it > > prints following information: > > ("ixgbe") already in use as a driver or alias. > > But I use "modinfo | grep ixgbe" can not find it. > > What is the problem? > > Zhihui > > > > 2008/6/23, Samuel Tu <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>>>: > > > > > > Hi Zhihui, > > > > Intel 82598EB (Oplin) is supported by ixgbe which has been > > integrated > > into snv_90. The pci ids supported by the current driver are: > > "pciex8086,10c6" > > "pciex8086,10c7" > > > > The CX4 adapter can also be supported by it but we've not add > > it it > > since we've not verified it on such adapter. > > > > To make it work, Please manually config it: > > 1) add_drv -i '"pciex8086,10dd" ixgbe > > 2) ifconfig ixgbe_# plumb up > > > > Please let me know the result. > > > > Thanks, > > Samuel > > > > zhihui Chen wrote: > > > > I have one 10G network adapter (Intel 82598EB) in my > > machine. But after installation of SNV_91, I can not find > > this adapter through "dladm show-dev". Following is the > > output of "dladm show-dev" and "scanpci" > > > > intel5# dladm show-dev > > LINK STATE SPEED DUPLEX > > e1000g0 up 1000Mb full > > e1000g1 up 1000Mb full > > intel5#/usr/X11R6/bin/scanpci > > ...... > > pci bus 0x0008 cardnum 0x00 function 0x00: vendor 0x8086 > > device 0x10dd > > Intel Corporation 82598EB 10 Gigabit AT CX4 Network Connection > > pci bus 0x0008 cardnum 0x00 function 0x01: vendor 0x8086 > > device 0x10dd > > Intel Corporation 82598EB 10 Gigabit AT CX4 Network Connection > > ...... > > > > anyone can tell me how to config my system to find the adapter? > > > > Thanks, > > Zhihui > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > networking-discuss mailing list > > [email protected] > > <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>> > > > > > > > > > > -- zhihui > > Intel OpenSolaris Team > > > > > > > > -- > > zhihui > > Intel OpenSolaris Team > > > > > > > > > > -- > > zhihui > > Intel OpenSolaris Team > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > networking-discuss mailing list > > [email protected] > > > > -- zhihui Intel OpenSolaris Team
_______________________________________________ networking-discuss mailing list [email protected]
