It is the (virtual) network infrastructure that imposes the payload restrictions, hence the MTU size. I case of QDIO the VSWITCH supports any MTU the attached (coupled) vNICs support, too. If you use a VSWITCH to interconnect guest virtual NICs with a distributed switched fabric over OSA Express, however, it is this connection that imposes your MTU limits - is OSA connected to a network supporting jumbo frames and have you configured the VM OSA TCP/IP definition accordingly? If yes you should be fine.
Best regards, Ingo Adlung Linux on 390 Port <[email protected]> wrote on 09.06.2005 07:33:13: > Hi,all > > Please teach me. > I want to comfirm VSWITCH's MTU size. > SLES9's eth0 connected to the VSWITCH is MTU 9000. > But VSWITCH's MTU size isn't diplayed on screen by using > "Q VSWITCH DETAILS" command. > > VSWITCH don't have MTU?? > > I want to use eth0 for MTU size 9000. > > Please teach me. > > Thank you. > ----- > K.M. > > > __________________________________ > Save the earth > http://pr.mail.yahoo.co.jp/ondanka/ > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
