I just downloaded the latest, greatest USB image and tried jumbo frames with it. The Myricom card is now working again. Probably should have done that first. It looks like the powerdown command turns off the computer again, too (that had also stopped working). I’m now seeing a significant speed boost when dealing with large files as a result.
Sorry for the false alarm. And you were right - all I had to do was play with the config entry. I just seem to remember something different that I had to do back when you were working on this commit. Either my memory was faulty or that was an experiment prior to your commit to the release. Again, sorry for the false alarm. Regards, John > On Aug 7, 2017, at 3:23 PM, Robert Mustacchi <[email protected]> wrote: > > On 8/7/17 12:08 , John Croix wrote: >> Hi Robert, >> >> A few years ago, you helped me with this very same problem :). Basically, >> when the card is initialized, the MTU is set and cannot be reset. That meant >> that you had to create some type of workaround due to the order in which >> services were started on SmartOS. I wish I could find the e-mail you sent >> me, but I don’t seem to have it anymore. I set a parameter in a file on the >> USB key, and you looked at that parameter to set the MTU when you >> initialized the card. >> >> Apparently that process doesn’t work anymore. When I upgraded my SmartOS >> distribution a few months ago, a bunch of the services didn’t come up. When >> I checked into it, I found out that the Myricom card wasn’t coming up >> because of the 9000 parameter. I eliminated the MTU parameter, letting it >> default back to 1500, and the system booted up just fine. >> >> When I get back home, I can retry the 9000 value to see what the exact error >> message is. The stupid thing that I did, though, was to not make a note of >> where that parameter was set. I thought that I had it in my notes, so when I >> removed it, I didn’t bother writing anything down about what file I removed >> it from or what the parameter name was. Now I’m not sure what I need to >> enable to get the error back again. I don’t suppose that you might still >> have a copy of that e-mail you sent me back in 2014 with the workaround that >> you integrated into the release, do you? > > Hi John, > > What I recall implementing wasn't a workaround, but I actually just > added the support to set the MTU through dladm set-linkprop and not > through the driver.conf property. At least, this is what I recall: > https://github.com/joyent/illumos-joyent/commit/5f23582. > > Presuming that the MTU is properly noted in the nic tag, this should > work. So it might be helpful to make sure that we have the nic tag's MTU > properly recorded and then figure out what's going on. > > Robert > ------------------------------------------- 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
