{"push_id":1262660843,"size":12,"distinct_size":12,"ref":"refs/heads/idosch-net-next","head":"4a032ffc3bf3ab9b4d2a756e534c403d1bd0aaa6","before":"ec178f66ebe3979b83f69ed5f6ab8a3db78509b7","commits":[{"sha":"3bada2a213bda2da3d1e586543ffbd50b38c4eae","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Make VLAN deletion function symmetric\n\nCommit 05978481e77e (\"mlxsw: spectrum: Create PVID vPort before\nregistering netdevice\") removed __mlxsw_sp_port_vlans_del() from the\ninit sequence of the driver, which forced it to be non-symmetric with\nregards to __mlxsw_sp_port_vlans_add().\n\nMake both functions symmetric as the constraint no longer exists.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/3bada2a213bda2da3d1e586543ffbd50b38c4eae"},{"sha":"a83a5aeef0ce0b813ef1a59354f26c333b4d6162","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Don't abort on first error when removing VLANs\n\nWhen removing VLANs from the VLAN-aware bridge we shouldn't abort on the\nfirst error, as we'll otherwise have resources that will never be freed.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/a83a5aeef0ce0b813ef1a59354f26c333b4d6162"},{"sha":"8ca8cf95cb0b4ab3d82946cad421550a2e0780df","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Configure learning for VLAN-aware bridge port\n\nWe are going to prevent the device from generating learning\nnotifications for a port that was configured with learning disabled.\n\nSince learning configuration is done per {Port, VID} we need to apply\nthe port's learning configuration for any VID that is added to the\nbridge port's VLAN filter list.\n\nWhen a VID is added to the VLAN filter list of a VLAN-aware bridge port,\nconfigure the {Port, VID} learning status according to the port's\nconfiguration. When the VID is removed, disable learning for the {Port,\nVID}.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/8ca8cf95cb0b4ab3d82946cad421550a2e0780df"},{"sha":"ff257661c4bb277476e0c3321e6e4c234a1d64ac","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Offload learning to the switch ASIC\n\nUp until now we simply stored the learning configuration of a bridge\nport in the driver and decided whether to learn a new FDB record based\non this value.\n\nHowever, this is sub-optimal in cases where learning is disabled on the\nbridge port, as the device repeatedly generates learning notifications\nfor the same record.\n\nInstead, offload the learning configuration to the device, thereby\npreventing it from generating notifications when learning is disabled.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/ff257661c4bb277476e0c3321e6e4c234a1d64ac"},{"sha":"beaca4f458dd4aa65da584ccfcd4b88333d7ed3d","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Remove unnecessary check in FDB processing\n\nWe now offload the learning configuration to the device and don't rely\non the driver to decide whether to learn the FDB record, so remove the\ncheck.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/beaca4f458dd4aa65da584ccfcd4b88333d7ed3d"},{"sha":"499c6888cb75fd88a3f965c7455c9a98da03b456","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Don't set learning when creating vPorts\n\nBefore commit 99724c18fc66 (\"mlxsw: spectrum: Introduce support for\nrouter interfaces\") we used to assign vFIDs to the created vPorts. Since\nthese vPorts were used for slow path traffic we had to disable learning\nfor them, as it doesn't make sense to have it enabled.\n\nThis is no longer the case and now vPorts are either used for router\ninterfaces (for which learning is disabled by the firmware) or bridge\nports (for which learning is explicitly enabled by the driver).\n\nTherefore, we can remove the learning configuration upon vPort creation.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/499c6888cb75fd88a3f965c7455c9a98da03b456"},{"sha":"4bcd07aa81cae7fccb21697b3da74e6630b1c3e4","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"switchdev: Support parent ID comparison for stacked devices\n\nswitchdev_port_same_parent_id() currently expects port netdevs, but we\nneed it to support stacked devices in the next patch, so drop the\nNO_RECURSE flag.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/4bcd07aa81cae7fccb21697b3da74e6630b1c3e4"},{"sha":"b12d7a0295b857881e5e142b001caf1d8b396697","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"bridge: switchdev: Add forward mark support for stacked devices\n\nswitchdev_port_fwd_mark_set() is used to set the 'offload_fwd_mark' of\nport netdevs so that packets being flooded by the device won't be\nflooded twice.\n\nIt works by assigning a unique identifier (the ifindex of the first\nbridge port) to bridge ports sharing the same parent ID. This prevents\npackets from being flooded twice by the same switch, but will flood\npackets through bridge ports belonging to a different switch.\n\nThis method is problematic when stacked devices are taken into account,\nsuch as VLANs. In such cases, a physical port netdev can have upper\ndevices being members in two different bridges, thus requiring two\ndifferent 'offload_fwd_mark's to be configured on the port netdev, which\nis impossible.\n\nThe main problem is that packet and netdev marking is performed at the\nphysical netdev level, whereas flooding occurs between bridge ports,\nwhich are not necessarily port netdevs.\n\nInstead, packet and netdev marking should really be done in the bridge\ndriver with the switch driver only telling it which packets it already\nforwarded. The bridge driver will mark such packets using the mark\nassigned to the ingress bridge port and will prevent the packet from\nbeing forwarded through any bridge port sharing the same mark (i.e.\nhaving the same parent ID).\n\nRemove the current switchdev 'offload_fwd_mark' implementation and\ninstead implement the proposed method. In addition, make rocker - the\nsole user of the mark - use the proposed method.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/b12d7a0295b857881e5e142b001caf1d8b396697"},{"sha":"63c66eb3c2686f6da90003f17cbe2632c8b18c7c","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Simplify traps definition\n\nInstead of copying & pasting the same struct initialization for every\nRx listener, just use a macro.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/63c66eb3c2686f6da90003f17cbe2632c8b18c7c"},{"sha":"ac8b8521d34b0fb88f54076d132d43af66f2b5d9","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Allow different traps to have different actions\n\nUp until now we only trapped packets to CPU, but we are going to allow\nsome packets to be mirrored (trap & forward) to CPU.\n\nExtend the Rx listener with 'action' member.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/ac8b8521d34b0fb88f54076d132d43af66f2b5d9"},{"sha":"83b0a10be601ca33d98cfcaff3ae4a32e9c241fe","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"mlxsw: spectrum: Mirror certain packets to CPU\n\nInstead of trapping certain packets to the CPU and then relying on it to\nflood them we can instead make the device mirror them.\n\nThe following packet types are mirrored:\n\n* DHCP: Broadcast packets that should be flooded by the device, but also\ntrapped in case CPU is running the DHCP server.\n\n* IGMP query: Multicast packets that need to be forwarded to other\nbridge ports, but also trapped so that receiving netdev will be marked\nas a router port by the bridge driver.\n\n* ARP request: Broadcast packets that should be forwarded to other\nbridge ports, but also trapped in case requested IP is of the local\nmachine.\n\n* ARP response: Unicast packets that should be forwarded by the bridge\nbut also trapped in case response is directed at us.\n\nSet the trap action of such packets to mirror and mark them using\n'offload_fwd_mark' to prevent the bridge driver from forwarding them\nitself.\n\nNote that OSPF packets are also marked despite their action being trap.\nThe reason for this is that the device traps such packets in the\npipeline after they were already flooded.\n\nSigned-off-by: Ido Schimmel <idosch@mellanox.com>","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/83b0a10be601ca33d98cfcaff3ae4a32e9c241fe"},{"sha":"4a032ffc3bf3ab9b4d2a756e534c403d1bd0aaa6","author":{"name":"Ido Schimmel","email":"47f98fbd7c1ff0617d70d2ed262591cfebfa5379@mellanox.com"},"message":"TMP: Revert \"fs/dcache.c: avoid soft-lockup in dput()\"\n\nThis reverts commit 47be61845c775643f1aa4d2a54343549f943c94c.\n\nNeed to look into this, but it causes a lot of warnings.","distinct":true,"url":"https://api.github.com/repos/idosch/linux/commits/4a032ffc3bf3ab9b4d2a756e534c403d1bd0aaa6"}]}
{"actor":{"display_login":"idosch"}}