From patchwork Wed Feb 3 07:41:21 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Ciara Loftus X-Patchwork-Id: 12063705 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=-11.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable 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 2F930C433DB for ; Wed, 3 Feb 2021 08:12:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DFA7764F67 for ; Wed, 3 Feb 2021 08:12:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232491AbhBCIMJ (ORCPT ); Wed, 3 Feb 2021 03:12:09 -0500 Received: from mga12.intel.com ([192.55.52.136]:59616 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232489AbhBCIMI (ORCPT ); Wed, 3 Feb 2021 03:12:08 -0500 IronPort-SDR: 9bO0n6TLp89VDD10bqojq10VwHanBF48j85ic78Qmf1dffWfXdimuSJtN86BB7NgodJLBTXGvO Q+iqHi7Fu8+w== X-IronPort-AV: E=McAfee;i="6000,8403,9883"; a="160170049" X-IronPort-AV: E=Sophos;i="5.79,397,1602572400"; d="scan'208";a="160170049" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Feb 2021 00:11:27 -0800 IronPort-SDR: A0QXg9CiX/FJIS+CQulNVZ0ISnBbaqpK/ZbGinREWMYnp50UIAdP4SWgqCxznyNdBIbj0TvQPs XPPxRU0h1Kxg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,397,1602572400"; d="scan'208";a="413932433" Received: from silpixa00399839.ir.intel.com (HELO localhost.localdomain) ([10.237.222.142]) by fmsmga002.fm.intel.com with ESMTP; 03 Feb 2021 00:11:25 -0800 From: Ciara Loftus To: netdev@vger.kernel.org, bpf@vger.kernel.org, magnus.karlsson@intel.com, bjorn@kernel.org, weqaar.a.janjua@intel.com Cc: daniel@iogearbox.net, Ciara Loftus Subject: [PATCH bpf-next v4 0/6] AF_XDP Packet Drop Tracing Date: Wed, 3 Feb 2021 07:41:21 +0000 Message-Id: <20210203074127.8616-1-ciara.loftus@intel.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org X-Patchwork-Delegate: bpf@iogearbox.net This series introduces tracing infrastructure for AF_XDP sockets (xsk). A trace event 'xsk_packet_drop' is created which can be enabled by toggling /sys/kernel/debug/tracing/events/xsk/xsk_packet_drop/enable When enabled and packets or empty packet buffers are dropped in the kernel, traces are generated which describe the reason for the packet drop, the netdev and qid information of the xsk which encountered the drop, and some more information depending on what type of drop was encountered that will tell the user why the packet was dropped. This information should help a user troubleshoot packet drops by providing an extra level of detail which is not available through use of simple counters Example traces: xsk_packet_drop: netdev: ve3213 qid 0 reason: packet too big: len 3000 max 2048 not_used 0 xsk_packet_drop: netdev: ve3213 qid 0 reason: invalid fill addr: addr 520192 not_used 0 not_used 0 xsk_packet_drop: netdev: ve9266 qid 0 reason: invalid tx desc: addr 0 len 4097 options 0 It was decided to use a single event 'xsk_packet_drop' to capture these three drop types. This means that for some of them, there is some redundant information in the trace marked as 'not_used'. An alternative to this would be to introduce 3 separate event types under xsk, each with their own appropriate trace format. Suggestions are welcome on which approach would be better to take. The event can be monitored using perf: perf stat -a -e xsk:xsk_packet_drop A selftest is added for each drop type. These tests provide the conditions to trigger the traces and ensure that the appropriate traces are generated. v4->v3: * Fixed selftest commits with correct logs * Fixed warnings reported by W=1 build: trace argument types and print formatting v2->v3: * Removed some traces which traced events which were not technically drops eg. when the rxq is full. * Introduced traces for descriptor validation on RX and TX and selftests for both v1->v2: * Rebase on top of Björn's cleanup series. * Fixed packet count for trace tests which don't need EOT frame. This series applies on commit 1132b9987a3f6c7c396633d5a675075911f1ce32 Ciara Loftus (6): xsk: add tracepoints for packet drops selftests/bpf: restructure setting the packet count selftests/bpf: add framework for xsk selftests selftests/bpf: XSK_TRACE_DROP_PKT_TOO_BIG test selftests/bpf: XSK_TRACE_INVALID_FILLADDR test selftests/bpf: XSK_TRACE_INVALID_DESC_TX test MAINTAINERS | 1 + include/linux/bpf_trace.h | 1 + include/trace/events/xsk.h | 73 ++++++++ include/uapi/linux/if_xdp.h | 6 + kernel/bpf/core.c | 1 + net/xdp/xsk.c | 7 +- net/xdp/xsk_buff_pool.c | 3 + net/xdp/xsk_queue.h | 4 + tools/include/uapi/linux/if_xdp.h | 6 + tools/testing/selftests/bpf/test_xsk.sh | 90 ++++++++- tools/testing/selftests/bpf/xdpxceiver.c | 206 +++++++++++++++++++-- tools/testing/selftests/bpf/xdpxceiver.h | 9 + tools/testing/selftests/bpf/xsk_prereqs.sh | 3 +- 13 files changed, 381 insertions(+), 29 deletions(-) create mode 100644 include/trace/events/xsk.h