From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-f41.google.com (mail-yw1-f41.google.com [209.85.161.41]) by dpdk.org (Postfix) with ESMTP id 9E37C4C8D for ; Tue, 2 Oct 2018 06:36:14 +0200 (CEST) Received: by mail-yw1-f41.google.com with SMTP id d126-v6so263114ywa.5 for ; Mon, 01 Oct 2018 21:36:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hIQgqG6gTVcVgkiQ9v5HZifYY50SPyIHeAMvE8spG/k=; b=c56YU4dSSrFsWcCdrcjxUorl0kfjTKGiDthd9OQ5FhBd93rS9lg7phJMM4FwZcQ7nQ 1m/wCSRPtZXF9twvqxXjIwv2tj2PHmjQtssHv/G5HqudMkEBlxrj97kMiSUxb1xen/h8 hEf054MKOYNic/mV5lLizz5KSLBF4kVMVSzJ5BSHdapf8pF4Z8oAOnIhL8T5+fsbAZjh UfulKryn94lTsVG9yY0kzyh+YYrYHRnEAw9BdqXV1mw/Z0hvtRZE0ZI3r3OQUAWLj5Ju /Be4x/5Mzd5ZeedMZxi514wS+xOHxku3zaOdOCFQcAnU/mPzw0m5gDYJp+JMVbqp9uku srBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hIQgqG6gTVcVgkiQ9v5HZifYY50SPyIHeAMvE8spG/k=; b=LnIsh+tbvIgmc/Jz2DojKNYm/lxZJFZLNTwNq+euwV595ZN/B6iTFmu1uYiLqbKGM/ v+9Ao4WizGkrJQ8tsL/dzTIZWk2VLZt6Nfk3OcDFC08K7EDtMgLIIWikehxajYhzwAg8 s3v1dyUALKg0Ax0BcXkYXuyTAUJ3BzcHpzwHZhh65pYEl2PIogPYES1meyqDrhhS+oxG B7sT8J19tejioGrdzgMFR4McvmYxbBqoihOCjDWEVC5UZvPsC7epPM+PLnLrG0XhRBXq fZgF3jJ2PNIECgqQYr6FrLg4LlcoF7IkqxwDYBkagsZt+x1ceR1Ax+m3tL6MgJRlXYf5 OapA== X-Gm-Message-State: ABuFfogLKxqmX4LuXzS00idcA2XiXxK/wP6/XrRv9GuEIBE1qrrIoPV9 jtVWhonFMzEFQ8CKAmGUSNUUzzNoZr/ajLDZMlw= X-Google-Smtp-Source: ACcGV61uT7ZWWDe+ky6ivdrp8W9cRgLQkFiNLSsMfBZE5EMKzbsioLaisKn3Nx+1+GJF6Q19NdDn71RhG2G3CfvqVA4= X-Received: by 2002:a81:a8c6:: with SMTP id f189-v6mr7817851ywh.350.1538454973803; Mon, 01 Oct 2018 21:36:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Cliff Burdick Date: Mon, 1 Oct 2018 21:36:02 -0700 Message-ID: To: Arvind Narayanan Cc: users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] rte_flow error after upgrading X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2018 04:36:14 -0000 Thanks, I will try that. I saw that patch, but couldn't find any working examples with vlan. In the other layers, such as Ethernet, zeroing out the source and dest has the effect of allowing all. However, the vlan on mellanox cards breaks that it seems because of the IB compatibility. I think the flow filtering example needs to be updated, since it will no longer work on these cards. If I get it working I'll submit a PR. On Mon, Oct 1, 2018, 21:28 Arvind Narayanan wrote: > It is because of a recent patch http://patchwork.dpdk.org/patch/36068/ > > If you don't care about VLAN action, just remove that action all together > and check the correctness of your code. > If all of them are going to q0 (and assuming isolation mode is not > enabled), then it is most likely because packets don't match any of the > rte_flow rules you created. > > A > > On Mon, Oct 1, 2018 at 11:20 PM Cliff Burdick wrote: > >> Hi, I upgraded to DPDK 18.05 from 17.11 and a previously-working rte_flow >> code now fails. I'm using the mlx5 driver, and when I do something similar >> to the rte_flow example code, the following error shows: >> >> "VLAN cannot be empty" >> >> I looked at the code in .drivers/net/mlx5/mlx5_flow.c, and it looks like >> it >> now complains when the mask isn't set on a VLAN flow layer. I tried >> setting >> the mask to 0xffff, and the error no longer shows, but packets are not >> classified properly either, and they all go to queue 0. Has anyone been >> able to get a working rte_flow queue classifier working with 18.05+? >> >