Apparently it’s not possible to set the value to 9000 using dladm. The output of “dladm show-linkprop -p mtu” under SmartOS shows the following: [root@68-05-ca-0a-2f-c5 ~]# dladm show-linkprop myri10ge0 -p mtu LINK PROPERTY PERM VALUE DEFAULT POSSIBLE myri10ge0 mtu rw 1500 1500 1500 I gave it a try, though [root@68-05-ca-0a-2f-c5 ~]# ifconfig myri10ge0 unplumb [root@68-05-ca-0a-2f-c5 ~]# dladm set-linkprop -p mtu=9000 myri10ge0 dladm: warning: cannot set link property 'mtu' on 'myri10ge0': operation not supported [root@68-05-ca-0a-2f-c5 ~]# uname -a SunOS 68-05-ca-0a-2f-c5 5.11 joyent_20140418T031241Z i86pc i386 i86pc
When I originally put the card into a Solaris 11.2 box, the MTU was 9000. After doing a point-to-point connection to SmartOS and configuring it, I now have to use a configuration file (/kernel/drv/myri10ge.conf) with the following contents to get a 9000 upper limit. # MTU - Jumbo Frames myri10ge_mtu_override=9000; According to the documentation (https://www.myricom.com/software/myri10ge/686-abbreviated-myri10ge-installation-for-solaris-10.html), 9000 is supposed to be the default (which isn’t what I saw with SmartOS). But, like I said, with the ability to put a configuration setting into /kernel/drv/myri10ge.conf in Solaris 11.2, I can explicitly set the upper limit. root@solaris11:~# dladm show-linkprop net0 -p mtu LINK PROPERTY PERM VALUE EFFECTIVE DEFAULT POSSIBLE net0 mtu rw 9000 9000 1500 9000 If I had the ability to create that file in SmartOS using SMF, my guess is that I’d be able to solve the problem. It looks like it would have to happen before the network milestone is hit, or maybe the devices milestone, but I’d need to make sure that it’s complete before the Myricom device driver is loaded. I know that you can create a prerequisite for a manifest, but I’m not sure how you interpose a manifest, if that’s even possible. Regards, John On Jul 5, 2014, at 10:35 AM, Garrett D'Amore via smartos-discuss <[email protected]> wrote: > Can you set the mtu with dladm? If config only changes the IP layer mtu. > The link layer maximum is configured with dladm. I don't recall the precise > name of the setting offhand and as I'm not in front of a computer I can't > check. > > Sent from my iPhone > > On Jul 4, 2014, at 9:03 PM, "John Croix via smartos-discuss" > <[email protected]> wrote: > >> I just installed a Myricom 10Gbe adapter into my SmartOS server, and I’m >> having an issue with the default MTU. According to Myricom documentation, >> the default MTU is supposed to be 9000. However, on my system, the default >> MTU is 1500. On a Solaris 11.2 (beta) box, it is properly set at 9000. It’s >> also 9000 on Linux by default. Attempting to increase it to 9000 yields an >> error: >> [root@68-05-ca-0a-2f-c5 /var/svc/log]# ifconfig myri10ge0 unplumb >> [root@68-05-ca-0a-2f-c5 /var/svc/log]# ifconfig myri10ge0 plumb >> [root@68-05-ca-0a-2f-c5 /var/svc/log]# ifconfig myri10ge0 mtu 9000 >> ifconfig: setifmtu: SIOCSLIFMTU: myri10ge0: Invalid argument >> [root@68-05-ca-0a-2f-c5 /var/svc/log]# ifconfig myri10ge0 >> myri10ge0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 11 >> inet 0.0.0.0 netmask 0 >> ether 0:60:dd:45:73:22 >> >> I read a discussion thread at >> https://www.mail-archive.com/[email protected]/msg14160.html >> that talks about the Myricom configuration file and the fact that it’s >> missing from /kernel/drv/myri10ge.conf. That’s definitely the case on my >> system. So I guess I have 2 questions: >> Is there a bug (aka "undocumented feature”) somewhere in the system that’s >> causing the MTU to be set to 1500 instead of 9000 and, if so, can it be >> corrected? >> Is there any way to get a configuration file into /kernel/drv that can >> persist across reboots, before the Myricom device driver is loaded? >> >> I’ve tried unloading the device driver, but it won’t work: >> [root@68-05-ca-0a-2f-c5 /]# ifconfig myri10ge0 unplumb >> [root@68-05-ca-0a-2f-c5 /]# modunload -i 224 >> can't unload the module: Device busy >> So I can’t force it that way. >> >> I thought about creating a SMF manifest that runs a script to create the >> configuration file prior to loading the device driver. However, I’m not sure >> what dependencies I’d set to ensure the order (so that the script does, in >> fact, run before the device driver is loaded) or whether such an approach >> would work. >> >> Does anybody happen to have any ideas on the matter? I’m not getting nearly >> the speed that I should as a result of this setting, and I really need to >> get this resolved. >> >> Thanks and regards, >> John >> >> smartos-discuss | Archives | Modify Your Subscription > > smartos-discuss | Archives | Modify Your Subscription ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
