<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> Hi all,<o:p></o:p> Regarding the list of patches I’ve sent, it’s mostly bug-fixes pulled from upstream and 4 fixes that made by-demand for HP urgent issues.<o:p></o:p> More specific details on purpose and mainly testing of these patches:<o:p></o:p> <![if !supportLists]>· <![endif]>2 patches that are required for HP certification – and are relevant for x86 redhat – so it is less urgent to integrate it to Ubuntu at the moment, sorry for the bother.<o:p></o:p> UBUNTU: SAUCE: (no-up) net/mlx4_core: Use low memory profile on kdump kernel<o:p></o:p> UBUNTU: SAUCE: (no-up) net/mlx4_en: Reduce memory consumption on kdump kernel<o:p></o:p> <![if !supportLists]>· <![endif]>This patch exposes the ability to disable blueflame. It help improving bi-directional IP forwarding test performance on mcdivitt – HP request.<o:p></o:p> UBUNTU: SAUCE: (no-up) net/mlx4_en: Disable blueflame using ethtool private flags<o:p></o:p> <![if !supportLists]>· <![endif]>4 patches that fix MAC modification handling issues – fixes an issue with bonding alb/tlb modes – HP request.<o:p></o:p> A simple test would be to set a tlb bond over 2 ports of mellanox NIC – and “make” bonding driver switch the role of active interface between the 2 interfaces by setting the ports up/down.<o:p></o:p> UBUNTU: SAUCE: (no-up) net/mlx4_en: current_mac isn't updated in port up<o:p></o:p> UBUNTU: SAUCE: (linux-next) net/mlx4_en: Fix mac_hash database inconsistency<o:p></o:p> net/mlx4_en: Protect MAC address modification with the state_lock mutex<o:p></o:p> net/mlx4_en: Fix errors in MAC address changing when port is down<o:p></o:p> <![if !supportLists]>· <![endif]>Without this patch, if probe_vf (mlx4_core module parameter) is being used (usually with a big number >= 8), <o:p></o:p> You’ll see such prints: “localhost systemd-udevd: worker [14567] /devices/pci0000:00/0000:00:02.0/0000:03:00.1 timeout; kill it”<o:p></o:p> net/mlx4_core: Defer VF initialization till PF is fully initialized<o:p></o:p> <![if !supportLists]>· <![endif]>Without this patch, when loading the mlx4_core with probed VF you’ll see these prints: “PCIe link width is x0, device supports x8”, and on VM “Unable to determine PCI device chain minimum BW”<o:p></o:p> net/mlx4_core: Don't issue PCIe speed/width checks for VFs<o:p></o:p> <![if !supportLists]>· <![endif]>Without this patch – when you attach a single port VF of “port 2” to a VM, and unload/load the mellanox driver you’ll observe the following error messages:<o:p></o:p> “mlx4_core 0000:04:00.0: vhcr command QP_ATTACH (0xf0b) slave:7 in_param 0x66b5a000 in_mod=0x1000086a, op_mod=0x0 failed with error:0, status -22”<o:p></o:p> net/mlx4_core: Adjust port number in qp_attach wrapper when detaching<o:p></o:p> <![if !supportLists]>· <![endif]>Way to reproduce: 1) Start VM and assign it VFx 2) Configure bonding between 2 ports of the VF 3) Assign IP to the bond 4) Shut down this VM 5) Start new VM and assign it VMy 6) Go over steps 2-3 for this VM 7) Try running rping between this VM and hypervisor (at this point rping does not work)<o:p></o:p> net/mlx4_core: Reset RoCE VF gids when guest driver goes down<o:p></o:p> <![if !supportLists]>· <![endif]>Configure: Load mlx4_core with “options mlx4_core port_type_array=2,2 debug_level=1 num_vfs=1,1,2 probe_vf=0,1,1 log_num_mgm_entry_size=-1”<o:p></o:p> Run rping client on the probed VF of port2 (rping -dvca 192.168.30.1 -C 1) – without this patch it would fail with the following error: “cma event RDMA_CM_EVENT_UNREACHABLE, error -110.<o:p></o:p> net/mlx4_core: Fix slave id computation for single port VF<o:p></o:p> <![if !supportLists]>· <![endif]>1) Run VPI on the Hypervisor, with opensm and ipoib running on the IB port<o:p></o:p> 2) Bring up the guest/VF<o:p></o:p> 3) Configure the guest<o:p></o:p> 4) Rping from guest as client – works.<o:p></o:p> 5) On the guest, unload ONLY the low level driver (mlx4_ib/mlx4_en) and bring it back up – bringing up mlx4_ib FIRST, then mlx4_en.<o:p></o:p> 6) Re-configure the guest interfaces<o:p></o:p> 7) Rping from guest as client. DOES NOT WORK<o:p></o:p> net/mlx4_core: Add UPDATE_QP SRIOV wrapper support<o:p></o:p> <![if !supportLists]>· <![endif]>Set up a bonding interface over an VXLAN encapsulating device with ConnectX3-Pro HW, Send traffic, and check with tcpdump that GSO is functioning.<o:p></o:p> bonding: Advertize vxlan offload features when supported<o:p></o:p> <![if !supportLists]>· <![endif]>Single ported VF are currently supported only when all HCA ports are set to Ethernet – such operation would fail, but without this patch it will return success (0). <o:p></o:p> net/mlx4_core: Fix the error flow when probing with invalid VF configuration<o:p></o:p> <![if !supportLists]>· <![endif]>Load the mlx4_core with the following module parameter “log_num_mgm_entry_size=-1” to enable vxlan offloads – no traffic will get to the RX side (i.e. tcpdump).<o:p></o:p> net/mlx4_en: Don't configure the HW vxlan parser when vxlan offloading isn't set<o:p></o:p> <![if !supportLists]>· <![endif]>Without this patches network interface names for port 2 of 2-port devices mellanox are inconsistent – HP requested this patch but I don’t think it’s their unique need.<o:p></o:p> Can be easily checked with a command as follows: $ grep . /sys/bus/pci/drivers/mlx4_core/0000\:24\:00.0/net/*/dev_id<o:p></o:p> Should return:<o:p></o:p> /sys/bus/pci/drivers/mlx4_core/0000:24:00.0/net/eth8/dev_id:0x0<o:p></o:p> /sys/bus/pci/drivers/mlx4_core/0000:24:00.0/net/eth9/dev_id:0x1<o:p></o:p> Instead of this buggy output without the patch:<o:p></o:p> /sys/bus/pci/drivers/mlx4_core/0000:24:00.0/net/p5p1/dev_id:0x0<o:p></o:p> /sys/bus/pci/drivers/mlx4_core/0000:24:00.0/net/rename13/dev_id:0x0<o:p></o:p> Revert "net/mlx4_en: Fix bad use of dev_id"<o:p></o:p> <![if !supportLists]>· <![endif]>Not sure about testing these three:<o:p></o:p> net/mlx4_core: Load the Eth driver first<o:p></o:p> net/mlx4_core: Keep only one driver entry release mlx4_priv<o:p></o:p> net/mlx4_core: Preserve pci_dev_data after __mlx4_remove_one()<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Best Regards,<o:p></o:p> Eyal.<o:p></o:p> <o:p> </o:p> From: Brian Fromme [mailto:brian.fromme@canonical.com] Sent: Saturday, July 26, 2014 12:38 AM To: Narinder Gupta; Rafael Tinoco Cc: Michael Miller; Dann Frazier; Raghuram Kota; Tim Gardner; Ming Lei; Eyal Perry; kernel-team Subject: Re: Trusty SRU - Mellanox refresh<o:p></o:p> <o:p> </o:p> <div> <div> That's an excellent question, Narinder. Eyal, Tim, Rafael, etc. Can you help us to understand how to test these patches? We can request that HP gets involved in the testing, but only if we can explain what these changes are and how to test them.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> thanks,<o:p></o:p> </div> <div> Brian<o:p></o:p> </div> <div> <o:p> </o:p> </div> </div> <div> <o:p> </o:p> <div> On Fri, Jul 25, 2014 at 3:06 PM, Narinder Gupta <<a href="mailto:narinder.gupta@canonical.com" target="_blank">narinder.gupta@canonical.com</a>> wrote:<o:p></o:p> <div> <div> Brian,<o:p></o:p> </div> Will you please brief me the changes we are suppose to test. I can ask HP to test and submit the results.<o:p></o:p> </div> <div> <o:p></o:p> <div> <div> <pre>Thanks and Regards,<o:p></o:p></pre> <pre>Narinder Gupta (PMP) <a href="mailto:narinder.gupta@canonical.com" target="_blank">narinder.gupta@canonical.com</a><o:p></o:p></pre> <pre>Canonical, Ltd. narindergupta [<a href="http://irc.freenode.net" target="_blank">irc.freenode.net</a>]<o:p></o:p></pre> <pre><a href="tel:%2B1.281.736.5150" target="_blank">+1.281.736.5150</a> narindergupta2007[skype]<o:p></o:p></pre> <pre><o:p> </o:p></pre> <pre>Ubuntu- Linux for human beings | <a href="http://www.ubuntu.com" target="_blank">www.ubuntu.com</a> | <a href="http://www.canonical.com" target="_blank">www.canonical.com</a><o:p></o:p></pre> </div> </div> <div> <div> <o:p> </o:p> <div> On Fri, Jul 25, 2014 at 3:56 PM, Brian Fromme <<a href="mailto:brian.fromme@canonical.com" target="_blank">brian.fromme@canonical.com</a>> wrote:<o:p></o:p> <div> <div> Oops, Narinder is the PM for McDivitt. Adding him to this thread.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> cheers,<o:p></o:p> </div> <div> Brian<o:p></o:p> </div> <div> <o:p> </o:p> </div> </div> <div> <o:p> </o:p> <div> On Fri, Jul 25, 2014 at 2:35 PM, Michael Miller <<a href="mailto:michael.miller@canonical.com" target="_blank">michael.miller@canonical.com</a>> wrote:<o:p></o:p> <div> I'm thinking it would Perry Hoffman and Scott Hinchley. I hope I spelled their names correctly.<o:p></o:p> </div> <div> <div> <div> <o:p> </o:p> <div> On Fri, Jul 25, 2014 at 3:31 PM, Brian Fromme <<a href="mailto:brian.fromme@canonical.com" target="_blank">brian.fromme@canonical.com</a>> wrote:<o:p></o:p> <div> <div> Yup. Adding Dann Frazier and Raghu. Can you guys help us to figure out who can integrate and test these on our McDivitt cartridge?<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> thanks,<o:p></o:p> </div> <div> Brian<o:p></o:p> </div> <div> <o:p> </o:p> </div> </div> <div> <div> <div> <o:p> </o:p> <div> On Fri, Jul 25, 2014 at 1:10 PM, Michael Miller <<a href="mailto:michael.miller@canonical.com" target="_blank">michael.miller@canonical.com</a>> wrote:<o:p></o:p> <div> Brian,<o:p></o:p> <div> Shouldn't this also go to the HP folks working the McDivitt issues? I don't have access to a McDivitt.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> -- mikem<o:p></o:p> </div> </div> <div> <div> <div> <o:p> </o:p> <div> On Fri, Jul 25, 2014 at 1:50 PM, Tim Gardner <<a href="mailto:tim.gardner@canonical.com" target="_blank">tim.gardner@canonical.com</a>> wrote:<o:p></o:p> Gents - I'd like some positive testing confirmation before I apply this to Trusty. rtg -- Tim Gardner <a href="mailto:tim.gardner@canonical.com" target="_blank">tim.gardner@canonical.com</a><o:p></o:p> </div> <o:p> </o:p> </div> </div> </div> </div> <o:p> </o:p> </div> </div> </div> </div> <o:p> </o:p> </div> </div> </div> </div> <o:p> </o:p> </div> </div> <o:p> </o:p> </div> </div> </div> </div> <o:p> </o:p> </div> </div> </body> </html>