1. 01 9月, 2021 1 次提交
  2. 29 8月, 2021 1 次提交
  3. 20 8月, 2021 1 次提交
  4. 17 8月, 2021 3 次提交
  5. 28 7月, 2021 1 次提交
    • A
      dev_ioctl: split out ndo_eth_ioctl · a7605370
      Arnd Bergmann 提交于
      Most users of ndo_do_ioctl are ethernet drivers that implement
      the MII commands SIOCGMIIPHY/SIOCGMIIREG/SIOCSMIIREG, or hardware
      timestamping with SIOCSHWTSTAMP/SIOCGHWTSTAMP.
      
      Separate these from the few drivers that use ndo_do_ioctl to
      implement SIOCBOND, SIOCBR and SIOCWANDEV commands.
      
      This is a purely cosmetic change intended to help readers find
      their way through the implementation.
      
      Cc: Doug Ledford <dledford@redhat.com>
      Cc: Jason Gunthorpe <jgg@ziepe.ca>
      Cc: Jay Vosburgh <j.vosburgh@gmail.com>
      Cc: Veaceslav Falico <vfalico@gmail.com>
      Cc: Andy Gospodarek <andy@greyhouse.net>
      Cc: Andrew Lunn <andrew@lunn.ch>
      Cc: Vivien Didelot <vivien.didelot@gmail.com>
      Cc: Florian Fainelli <f.fainelli@gmail.com>
      Cc: Vladimir Oltean <olteanv@gmail.com>
      Cc: Leon Romanovsky <leon@kernel.org>
      Cc: linux-rdma@vger.kernel.org
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NJason Gunthorpe <jgg@nvidia.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a7605370
  6. 25 7月, 2021 1 次提交
    • G
      octeontx2-pf: Fix interface down flag on error · 69f0aeb1
      Geetha sowjanya 提交于
      In the existing code while changing the number of TX/RX
      queues using ethtool the PF/VF interface resources are
      freed and reallocated (otx2_stop and otx2_open is called)
      if the device is in running state. If any resource allocation
      fails in otx2_open, driver free already allocated resources
      and return. But again, when the number of queues changes
      as the device state still running oxt2_stop is called.
      In which we try to free already freed resources leading
      to driver crash.
      This patch fixes the issue by setting the INTF_DOWN flag on
      error and free the resources in otx2_stop only if the flag is
      not set.
      
      Fixes: 50fe6c02 ("octeontx2-pf: Register and handle link notifications")
      Signed-off-by: NGeetha sowjanya <gakula@marvell.com>
      Signed-off-by: NSunil Kovvuri Goutham <Sunil.Goutham@cavium.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      69f0aeb1
  7. 02 7月, 2021 2 次提交
  8. 16 6月, 2021 1 次提交
  9. 15 6月, 2021 1 次提交
    • S
      octeontx2-pf: Cleanup flow rule management · 9917060f
      Sunil Goutham 提交于
      Current MCAM allocation scheme allocates a single lot of
      MCAM entries for ntuple filters, unicast filters and VF VLAN
      rules. This patch attempts to cleanup this logic by segregating
      MCAM rule allocation and management for Ntuple rules and unicast,
      VF VLAN rules. This segregation will result in reusing most of
      the logic for supporting ntuple filters for VF devices.
      
      Also added debug messages for MCAM entry allocation failures.
      Signed-off-by: NSunil Goutham <sgoutham@marvell.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9917060f
  10. 12 6月, 2021 2 次提交
  11. 19 3月, 2021 2 次提交
    • G
      octeontx2-pf: Clear RSS enable flag on interace down · f12098ce
      Geetha sowjanya 提交于
      RSS configuration can not be get/set when interface is in down state
      as they required mbox communication. RSS enable flag status
      is used for set/get configuration. Current code do not clear the
      RSS enable flag on interface down which lead to mbox error while
      trying to set/get RSS configuration.
      
      Fixes: 85069e95 ("octeontx2-pf: Receive side scaling support")
      Signed-off-by: NGeetha sowjanya <gakula@marvell.com>
      Signed-off-by: NHariprasad Kelam <hkelam@marvell.com>
      Signed-off-by: NSunil Kovvuri Goutham <sgoutham@marvell.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f12098ce
    • N
      octeontx2-pf: Add tc flower hardware offload on ingress traffic · 1d4d9e42
      Naveen Mamindlapalli 提交于
      This patch adds support for tc flower hardware offload on ingress
      traffic. Since the tc-flower filter rules use the same set of MCAM
      rules as the n-tuple filters, the n-tuple filters and tc flower
      rules are mutually exclusive. When one of the feature is enabled
      using ethtool, the other feature is disabled in the driver. By default
      the driver enables n-tuple filters during initialization.
      
      The following flow keys are supported.
          -> Ethernet: dst_mac
          -> L2 proto: all protocols
          -> VLAN (802.1q): vlan_id/vlan_prio
          -> IPv4: dst_ip/src_ip/ip_proto{tcp|udp|sctp|icmp}/ip_tos
          -> IPv6: ip_proto{icmpv6}
          -> L4(tcp/udp/sctp): dst_port/src_port
      
      The following flow actions are supported.
          -> drop
          -> accept
          -> redirect
          -> vlan pop
      
      The flow action supports multiple actions when vlan pop is specified
      as the first action. The redirect action supports redirecting to the
      PF/VF of same PCI device. Redirecting to other PCI NIX devices is not
      supported.
      
      Example #1: Add a tc filter rule to drop UDP traffic with dest port 80
          # ethtool -K eth0 hw-tc-offload on
          # tc qdisc add dev eth0 ingress
          # tc filter add dev eth0 protocol ip parent ffff: flower ip_proto \
                udp dst_port 80 action drop
      
      Example #2: Add a tc filter rule to redirect ingress traffic on eth0
      with vlan id 3 to eth6 (ex: eth0 vf0) after stripping the vlan hdr.
          # ethtool -K eth0 hw-tc-offload on
          # tc qdisc add dev eth0 ingress
          # tc filter add dev eth0 parent ffff: protocol 802.1Q flower \
                vlan_id 3 vlan_ethtype ipv4 action vlan pop action mirred \
                ingress redirect dev eth6
      
      Example #3: List the ingress filter rules
          # tc -s filter show dev eth4 ingress
      
      Example #4: Delete tc flower filter rule with handle 0x1
          # tc filter del dev eth0 ingress protocol ip pref 49152 \
            handle 1 flower
      Signed-off-by: NNaveen Mamindlapalli <naveenm@marvell.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1d4d9e42
  12. 12 2月, 2021 4 次提交
    • H
      octeontx2-pf: cn10k: Get max mtu supported from admin function · ab58a416
      Hariprasad Kelam 提交于
      CN10K supports max MTU of 16K on LMAC links and 64k on LBK
      links and Octeontx2 silicon supports 9K mtu on both links.
      Get the same from nix_get_hw_info mbox message in netdev probe.
      
      This patch also calculates receive buffer size required based
      on the MTU set.
      Signed-off-by: NHariprasad Kelam <hkelam@marvell.com>
      Signed-off-by: NSubbaraya Sundeep <sbhatta@marvell.com>
      Signed-off-by: NGeetha sowjanya <gakula@marvell.com>
      Signed-off-by: NSunil Goutham <sgoutham@marvell.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ab58a416
    • G
      octeontx2-pf: cn10k: Use LMTST lines for NPA/NIX operations · 4c236d5d
      Geetha sowjanya 提交于
      This patch adds support to use new LMTST lines for NPA batch free
      and burst SQE flush. Adds new dev_hw_ops structure to hold platform
      specific functions and create new files cn10k.c and cn10k.h.
      Signed-off-by: NGeetha sowjanya <gakula@marvell.com>
      Signed-off-by: NSunil Goutham <sgoutham@marvell.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4c236d5d
    • G
      octeontx2-pf: cn10k: Map LMTST region · 6e8ad438
      Geetha sowjanya 提交于
      On CN10K platform transmit/receive buffer alloc and free from/to hardware
      had changed to support burst operation. Whereas pervious silicon's only
      support single buffer free at a time.
      To Support the same firmware allocates a DRAM region for each PF/VF for
      storing LMTLINES. These LMTLINES are used for NPA batch free and for
      flushing SQE to the hardware.
      PF/VF LMTST region is accessed via BAR4. PFs LMTST region is followed
      by its VFs mbox memory. The size of region varies from 2KB to 256KB based
      on number of LMTLINES configured.
      
      This patch adds support for
      - Mapping PF/VF LMTST region.
      - Reserves 0-71 (RX + TX + XDP) LMTST lines for NPA batch
        free operation.
      - Reserves 72-512 LMTST lines for NIX SQE flush.
      Signed-off-by: NGeetha sowjanya <gakula@marvell.com>
      Signed-off-by: NSunil Goutham <sgoutham@marvell.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6e8ad438
    • S
      octeontx2-pf: cn10k: Add mbox support for CN10K · facede82
      Subbaraya Sundeep 提交于
      Firmware allocates memory regions for PFs and VFs in DRAM.
      The PFs memory region is used for AF-PF and PF-VF mailbox.
      This mbox facilitate communication between AF-PF and PF-VF.
      
      On CN10K platform:
      The DRAM region allocated to PF is enumerated as PF BAR4 memory.
      PF BAR4 contains AF-PF mbox region followed by its VFs mbox region.
      AF-PF mbox region base address is configured at RVU_AF_PFX_BAR4_ADDR
      PF-VF mailbox base address is configured at
      RVU_PF(x)_VF_MBOX_ADDR = RVU_AF_PF()_BAR4_ADDR+64KB. PF access its
      mbox region via BAR4, whereas VF accesses PF-VF DRAM mailboxes via
      BAR2 indirect access.
      
      On CN9XX platform:
      Mailbox region in DRAM is divided into two parts AF-PF mbox region and
      PF-VF mbox region i.e all PFs mbox region is contiguous similarly all
      VFs.
      The base address of the AF-PF mbox region is configured at
      RVU_AF_PF_BAR4_ADDR.
      AF-PF1 mbox address can be calculated as RVU_AF_PF_BAR4_ADDR * mbox
      size.
      The base address of PF-VF mbox region for each PF is configure at
      RVU_AF_PF(0..15)_VF_BAR4_ADDR.PF access its mbox region via BAR4 and its
      VF mbox regions from RVU_PF_VF_BAR4_ADDR register, whereas VF access its
      mbox region via BAR4.
      
      This patch changes mbox initialization to support both CN9XX and CN10K
      platform.
      The patch also adds new hw_cap flag to setting hw features like TSO etc
      and removes platform specific name from the PF/VF driver name to make it
      appropriate for all supported platforms
      
      This patch also removes platform specific name from the PF/VF driver name
      to make it appropriate for all supported platforms
      Signed-off-by: NSubbaraya Sundeep <sbhatta@marvell.com>
      Signed-off-by: NGeetha sowjanya <gakula@marvell.com>
      Signed-off-by: NSunil Goutham <sgoutham@marvell.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      facede82
  13. 11 2月, 2021 1 次提交
  14. 29 1月, 2021 1 次提交
  15. 21 11月, 2020 1 次提交
  16. 18 11月, 2020 5 次提交
  17. 01 10月, 2020 2 次提交
  18. 24 9月, 2020 1 次提交
  19. 02 9月, 2020 1 次提交
  20. 25 8月, 2020 1 次提交
  21. 29 7月, 2020 1 次提交
  22. 01 5月, 2020 1 次提交
  23. 26 3月, 2020 1 次提交
  24. 24 3月, 2020 4 次提交