From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 413A543052 for ; Fri, 18 Aug 2023 05:33:50 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 093F340395; Fri, 18 Aug 2023 05:33:50 +0200 (CEST) Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) by mails.dpdk.org (Postfix) with ESMTP id 29D8040156 for ; Fri, 18 Aug 2023 05:33:49 +0200 (CEST) Received: by mail-lf1-f51.google.com with SMTP id 2adb3069b0e04-4ff8936d247so133177e87.0 for ; Thu, 17 Aug 2023 20:33:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692329628; x=1692934428; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Zz2lwP2gvnq0fbGyMtFOhdoD3X63tQ5nkn2mOEpGR3g=; b=RJfxUm7yW3OmWNtlPWAYSmGIRiCeXErJ0msTkcT9OJ8y7hqSpB0A6ILOCwknVBFzu4 2lpifPWuIPElL4QZ+rXNUf3xcGBrvPUcKgHZVJ3cA3SlbnICGojkWHouYi86WD8PUvjV 6SV0RM/pI3BmzE9zeAqS9HP1ax4CiYgpGzPvjIEZlnu4ySM4pw0jcQQVNQPH2GuiKgBg bv41n1osj1MQxKQpaqG4isiNOjUhr1P9BUOJGUyz06Iqr6749jrX5Q02AcpDKw6l1Qtb oors2vpH/2G00shtZ3tlAKqZ9rfRHp4YvjJgPPyb0Ra08kAn3yc6EuMTxMDDN6JeDGcL qGCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692329628; x=1692934428; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Zz2lwP2gvnq0fbGyMtFOhdoD3X63tQ5nkn2mOEpGR3g=; b=UrfsaTIYdUs1iMql13sdC86SbbI0/rh2h8rMfBJzl+D5ehDScNFCu4tbcRsmz4WSDv rAIpCKPyUNvGtYbADeXkMuWk+UdzUXFW1aCInG0eScHQWG9xiTKy8vcQYRa5CEqunL9X 1JseWvqpO51LuzyDo/7/rkD3Ft2BXGHtPYv8iJ0jA+eAD5K7+krBB9h2x5e6DNKn8SKI D+A/Yz6dMcR0hl4zfHg/3eet+2FZZgV6M5XZQ8GO9lZSXKOLenqh3zHPRB5aVcZvdNG+ D/uZaJIwyQQUnyZ7JxF/NhWXYxTrwNsisQ4Q7TCWHSA/pky7R+r8XhWuEeS26VvMd+OC pk/w== X-Gm-Message-State: AOJu0YxpDopTPEhW8PSJktaYa3flb7ovIPaIhieRFimH9xpkUXif3SDS U2SFlQxBT4cpq2ZpCyIF1a6NlpQsqsMyPFPRKZcjnRmVrJeyIw== X-Google-Smtp-Source: AGHT+IFX/CR6dEklfuJXA0YVo3ZBB8vT6nW5LKNx0fLhxDmdrVeLD4lQ4dqEt8ixOG8zQCG8//6htvHmEPJ6iZaP6VE= X-Received: by 2002:a19:740a:0:b0:4fd:cab4:7d13 with SMTP id v10-20020a19740a000000b004fdcab47d13mr688771lfe.0.1692329628087; Thu, 17 Aug 2023 20:33:48 -0700 (PDT) MIME-Version: 1.0 From: narsimharaj pentam Date: Fri, 18 Aug 2023 09:03:36 +0530 Message-ID: Subject: VLAN filtering in mlx5 To: users@dpdk.org Content-Type: multipart/alternative; boundary="0000000000005349d906032a32b4" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --0000000000005349d906032a32b4 Content-Type: text/plain; charset="UTF-8" Hi We are using a mellanox mlx5 card (firmware version: 16.35.1012) with mlx5_pci driver. Enabled multiple ports DPDK port 0 (internally referred as slot 1 port 0: s1p0) and DPDK port 1(slot 0 port 0 : s0p0). Multiple vlans are created on each of these interfaces , s0p0.100, s0p0.101,s0p0.102 and s0p1.200,s0p1.201,s0p1.202. In our network we receive broadcast (ARP) and multicast(ICMPV6 for neighbour discovery) on port 0 and port 1. At the DPDK application we are observing the packets intended for interface s0p0.100 are landing on other vlan interfaces s0p0.101,sop0.102. The VLAN traffic is not segregated accordingly. Do we support VLAN filtering in mlx5 ? Came across VLAN filtering "vlan_filter_set" , will this help to drop unintended VLAN traffic ? or Do we need to create any VLAN specific rte flows in addition to the vlan filter set ? If rte flows are needed what should be rte_flow_action ? Thanks - Narsimha --0000000000005349d906032a32b4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

We are using a mellanox mlx5 card (firmwar= e version: 16.35.1012) with mlx5_pci driver.=C2=A0 Enabled multiple ports = =C2=A0DPDK port 0 (internally referred as slot 1 port 0: s1p0) =C2=A0and DP= DK port 1(slot 0 port 0 : s0p0). Multiple vlans are created on each of thes= e interfaces , s0p0.100, s0p0.101,s0p0.102 =C2=A0and s0p1.200,s0p1.201,s0p1= .202.

In our network we receive broadcast (ARP) and multicast= (ICMPV6 for neighbour discovery) on port 0 and port 1. At the DPDK applicat= ion we are observing the packets intended for interface s0p0.100 are =C2=A0= landing on other vlan interfaces s0p0.101,sop0.102. The VLAN traffic is not= segregated accordingly.

Do we support VLAN filtering in mlx5 ?

Came across VLAN filtering "vlan_filter_set"= , will this help to drop unintended VLAN traffic ? or=C2=A0 Do we need to = create any VLAN specific rte flows in addition to the vlan filter set ?=C2= =A0

If rte flows are needed what should = be=C2=A0 rte_flow_action ?=C2=A0

Thanks
= - Narsimha


--0000000000005349d906032a32b4--