From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 96B5EC43381 for ; Thu, 21 Feb 2019 16:32:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 609042084D for ; Thu, 21 Feb 2019 16:32:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="KH3HDu4v" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727017AbfBUQcF (ORCPT ); Thu, 21 Feb 2019 11:32:05 -0500 Received: from mail-yw1-f66.google.com ([209.85.161.66]:45555 "EHLO mail-yw1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725932AbfBUQcE (ORCPT ); Thu, 21 Feb 2019 11:32:04 -0500 Received: by mail-yw1-f66.google.com with SMTP id d190so11024625ywd.12 for ; Thu, 21 Feb 2019 08:32:04 -0800 (PST) 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=j8f7tMqO2caV4YbavXhb7PZz6OgGfe3YWLn9SimXzOs=; b=KH3HDu4vofbL/nGAjz03YOW0esYiBR5z7btJ3n8+otbXz6cApLsbpc44dHH3BCV2HO M7OhSJTc/trYSYY8D0PcNpALZRfGVuRjKz+5ttVj1cNbJcBLy6RchFsBPLuuJAsHwTWD B7ytLkdzF4qEYs8v2mEBld9yCZe9ZFDQwlzVuQ5l6gjMIDDvBDSLD3ETyMpqmhL9HJco BuUhDyzQrtvbuZZn0ys/5riIsIaln3Wjt4DOpHxLy655oMUPLHhRqAuFZJlOshSUPZZU /zExuc/G66kURUJ7K9AYMFbmA/t51ipG+2lNTny5NzcjcPmIPgVTJnP91p/3XTmN5wkM 62yQ== 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=j8f7tMqO2caV4YbavXhb7PZz6OgGfe3YWLn9SimXzOs=; b=e6z7NE0u5jVVCN4P3gjS4UMYdniju7MilpD9kZrCHxKyfncJegO2l7owSovTFH7FAM Eh1zUzBBSHI+BVX/O3kyg9v3bvsW6BynY5psa+inddR3X0aVuPwYAoxnoSssE87Ofjsw K2Tpv9HIDjeT6u6y7R2Yn+Lbg5MMszRm5g+xQFGO+gxzzoYEwEv39LMfLKq2Dh30DySU BoaPkpYSapqffgzPHezvemky7oWvZqMsE9ufhLDApST8T/83eKR0KLEcPBkU0++ulOrg 36usKu60ew+NEMmk9zZCFKBm2Kshe3qnqNgKSDWqvhrof1sHTmBdijuPsXKdbdJ9ddZf FvqA== X-Gm-Message-State: AHQUAub9jXrOXtJkNEEc6KHsCqlbCDO/UbdKIxlJhUhEZ9PPrcxg7tWB BpRNvABMPPdGg5in8nxf90eysKqQYkn23IKw6O+qrI98 X-Google-Smtp-Source: AHgI3IZUu+jmF8FFyUEBQix5PDplgF5lF5zSP5CSACK+kTqhqx445Ty24mpUJiQViVAle6c3cptxks26SGhOiJeFA/s= X-Received: by 2002:a0d:d705:: with SMTP id z5mr33553141ywd.400.1550766724096; Thu, 21 Feb 2019 08:32:04 -0800 (PST) MIME-Version: 1.0 References: <1550715283-23579-1-git-send-email-xiangxia.m.yue@gmail.com> <1550715283-23579-2-git-send-email-xiangxia.m.yue@gmail.com> In-Reply-To: <1550715283-23579-2-git-send-email-xiangxia.m.yue@gmail.com> From: Or Gerlitz Date: Thu, 21 Feb 2019 18:31:53 +0200 Message-ID: Subject: Re: [PATCH net-next 2/5] net/mlx5e: Make the log friendly when decapsulation offload not supported To: Tonghao Zhang Cc: Saeed Mahameed , Linux Netdev List Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Feb 21, 2019 at 3:42 PM wrote: > > From: Tonghao Zhang > > If we try to offload decapsulation actions to VFs hw, we get the log [1]. but the switching was on the tunnel type (if (tunnel_type == [...]) - what rules caused you to get here? what was the ingress device and what was the egress (mirred) device? > It's not friendly, because the kind of net device is null, and we don't > know what '0' means. > > [1] "mlx5_core 0000:05:01.2 vf_0: decapsulation offload is not supported for net device (0)"