From patchwork Wed Jan 24 16:49:15 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Puranjay Mohan X-Patchwork-Id: 13529408 Received: from mail-wm1-f52.google.com (mail-wm1-f52.google.com [209.85.128.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 92C6A46AA; Wed, 24 Jan 2024 16:49:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.52 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706114998; cv=none; b=QnoAiKrIMFpSWNleSbvMQhQYl4ulfB3e8OQnrJ4LCaEKm1DQoM1MPhRflmz5fnBgkQVpC6kjFhi2ZeohaEUK2HEeVHUIvG0KIzj8H/btO4HJmwnDvWyZWMIelvGcflCjWeKVrZNJuVIjGo4Ov7goalqL4uv0GbeK7VPXYLsQcwg= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706114998; c=relaxed/simple; bh=LVqTlDePOqCttJ74bFZOShfKzhmStjwMXCLSC09q1DI=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=AtYcLxgliTzy4jSinuMMDF8WbQy9YrSk4ahlgoMYTml1fMTA9Z0UtBYxBd8YTl3zaIpQ9BpbLMYGGxTbiSuxZ9yUDUxxGYtP5rTHMw3IRFn0TPIKmIWLFDNtJKxZK1HTwon0FQbaJqfUvFg6tWams/oZoIDAUVsn9LnWF5er6EY= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=Db89gnIT; arc=none smtp.client-ip=209.85.128.52 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Db89gnIT" Received: by mail-wm1-f52.google.com with SMTP id 5b1f17b1804b1-40e7e2e04f0so62508335e9.1; Wed, 24 Jan 2024 08:49:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706114995; x=1706719795; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=AK12Jgt9Qs3cXgEF+94VzkzqMIZGZUHiVBTJd0+rqq8=; b=Db89gnITLcYGwizY0Ie5O5sxHcg0oc75dV7D3IedfhP6fSrF98fF/29ZbSliyYLpm6 r5S/oVSXl0KiSshGKXPcuyB0+pXm4d+J9x5+wM4Q4rxDVfNa4JwlL5K4hCGO6TuzRQck uFDlW/iFDqA0rNBPBhSFjqzuTldtu+wj4bAi8OomqlmdDL1fDgpFmWtgB3SYqmANql5s Uo5s6BS53agsMQDQGeXRS3hX9lLXKeVLvtIjlKibdj6WegtSVFXBU9laW4PgHSEin3Zi Rle7S72iTY/Xpm+RyEccgP21rli2YJPr8CNbQfj8G4FHJGhKDXE3W5l/yHly47oOG7rs 7OZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706114995; x=1706719795; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=AK12Jgt9Qs3cXgEF+94VzkzqMIZGZUHiVBTJd0+rqq8=; b=ralV0USK+HDiv/bVGv1JriwGaAY0SoWu+HJSIkKPFiZt/ZG4Y2Ae9ONlWKr9blzzi5 ux08mviJYa71A3/LltKnO1b99bEJLfbIDrR+t+0X8M2RjLK2ggqnl9nVdNK06+B8cgLT mVV8QUAv1FyYuicawd4CbB53zhOnIi9Io4TXHqVv84IixVcDlpPEyx9t7yV7FiC9dY+n HNdzzUXXMhyyi/5pjPLh/zb97qPD1gzIwvIE4XbEej4p/dnwfc53xc/WvuKEgxqlawdn PbWFTUc9yQCNVgXF829gsTR38LlLOYP3KuhNa/dV/rZHLXSK7sk35T4BzWkhzoN1RZXM k6cQ== X-Gm-Message-State: AOJu0YwFSGztDZhYgqQcaawdnj3O1l9EydQOnqm/mI/pUWHmK4ro23lR Hig1RCThACyVUPL488Ua5aXF9j0QCbafawwPJ1f6dHPamGnKlR2lN2nq3+Kd4IdCWw== X-Google-Smtp-Source: AGHT+IF0qMHorF1IdcA4gs+A2fvFwgDCfh/qMRAmjTrbfj1GdFq165IF/JoMBwK3x+AMjw2F7u1NBw== X-Received: by 2002:a05:600c:3797:b0:40e:5600:2133 with SMTP id o23-20020a05600c379700b0040e56002133mr1609865wmr.72.1706114994399; Wed, 24 Jan 2024 08:49:54 -0800 (PST) Received: from localhost (54-240-197-231.amazon.com. [54.240.197.231]) by smtp.gmail.com with ESMTPSA id p22-20020a05600c359600b0040e4a7a7ca3sm194975wmq.43.2024.01.24.08.49.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jan 2024 08:49:54 -0800 (PST) From: Puranjay Mohan To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev, song@kernel.org, catalin.marinas@arm.com, mark.rutland@arm.com, bpf@vger.kernel.org, kpsingh@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, xukuohai@huaweicloud.com Cc: puranjay12@gmail.com Subject: [PATCH bpf-next v6 0/2] bpf, arm64: use BPF prog pack allocator in BPF JIT Date: Wed, 24 Jan 2024 16:49:15 +0000 Message-Id: <20240124164917.119997-1-puranjay12@gmail.com> X-Mailer: git-send-email 2.40.1 Precedence: bulk X-Mailing-List: bpf@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Patchwork-Delegate: bpf@iogearbox.net Changes in V5 => V6: V5: https://lore.kernel.org/all/20230908144320.2474-1-puranjay12@gmail.com/ 1. Implement a text poke api to reduce code repeatition. 2. Use flush_icache_range() in place of caches_clean_inval_pou() in the functions that modify code. 3. Optimize the bpf_jit_free() by not copying the all instructions on the rw image to the ro_image Changes in V4 => v5: 1. Remove the patch for making prog pack allocator portable as it will come through the RISCV tree[1]. 2. Add a new function aarch64_insn_set() to be used in bpf_arch_text_invalidate() for putting illegal instructions after a program is removed. The earlier implementation of bpf_arch_text_invalidate() was calling aarch64_insn_patch_text_nosync() in a loop and making it slow because each call invalidated the cache. Here is test_tag now: [root@ip-172-31-6-176 bpf]# time ./test_tag test_tag: OK (40945 tests) real 0m19.695s user 0m1.514s sys 0m17.841s test_tag without these patches: [root@ip-172-31-6-176 bpf]# time ./test_tag test_tag: OK (40945 tests) real 0m21.487s user 0m1.647s sys 0m19.106s test_tag in the previous version was really slow > 2 minutes. see [2] 3. Add cache invalidation in aarch64_insn_copy() so other users can call the function without worrying about the cache. Currently only bpf_arch_text_copy() is using it, but there might be more users in the future. Chanes in V3 => V4: Changes only in 3rd patch 1. Fix the I-cache maintenance: Clean the data cache and invalidate the i-Cache only *after* the instructions have been copied to the ROX region. Chanes in V2 => V3: Changes only in 3rd patch 1. Set prog = orig_prog; in the failure path of bpf_jit_binary_pack_finalize() call. 2. Add comments explaining the usage of the offsets in the exception table. Changes in v1 => v2: 1. Make the naming consistent in the 3rd patch: ro_image and image ro_header and header ro_image_ptr and image_ptr 2. Use names dst/src in place of addr/opcode in second patch. 3. Add Acked-by: Song Liu in 1st and 2nd patch. BPF programs currently consume a page each on ARM64. For systems with many BPF programs, this adds significant pressure to instruction TLB. High iTLB pressure usually causes slow down for the whole system. Song Liu introduced the BPF prog pack allocator[3] to mitigate the above issue. It packs multiple BPF programs into a single huge page. It is currently only enabled for the x86_64 BPF JIT. This patch series enables the BPF prog pack allocator for the ARM64 BPF JIT. ==================================================== Performance Analysis of prog pack allocator on ARM64 ==================================================== To test the performance of the BPF prog pack allocator on ARM64, a stresser tool[4] was built. This tool loads 8 BPF programs on the system and triggers 5 of them in an infinite loop by doing system calls. The runner script starts 20 instances of the above which loads 8*20=160 BPF programs on the system, 5*20=100 of which are being constantly triggered. In the above environment we try to build Python-3.8.4 and try to find different iTLB metrics for the compilation done by gcc-12.2.0. The source code[5] is configured with the following command: ./configure --enable-optimizations --with-ensurepip=install Then the runner script is executed with the following command: ./run.sh "perf stat -e ITLB_WALK,L1I_TLB,INST_RETIRED,iTLB-load-misses -a make -j32" This builds Python while 160 BPF programs are loaded and 100 are being constantly triggered and measures iTLB related metrics. The output of the above command is discussed below before and after enabling the BPF prog pack allocator. The tests were run on qemu-system-aarch64 with 32 cpus, 4G memory, -machine virt, -cpu host, and -enable-kvm. Results ------- Before enabling prog pack allocator: ------------------------------------ Performance counter stats for 'system wide': 333278635 ITLB_WALK 6762692976558 L1I_TLB 25359571423901 INST_RETIRED 15824054789 iTLB-load-misses 189.029769053 seconds time elapsed After enabling prog pack allocator: ----------------------------------- Performance counter stats for 'system wide': 190333544 ITLB_WALK 6712712386528 L1I_TLB 25278233304411 INST_RETIRED 5716757866 iTLB-load-misses 185.392650561 seconds time elapsed Improvements in metrics ----------------------- Compilation time ---> 1.92% faster iTLB-load-misses/Sec (Less is better) ---> 63.16% decrease ITLB_WALK/1000 INST_RETIRED (Less is better) ---> 42.71% decrease ITLB_Walk/L1I_TLB (Less is better) ---> 42.47% decrease [1] https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=for-next&id=20e490adea279d49d57b800475938f5b67926d98 [2] https://lore.kernel.org/all/CANk7y0gcP3dF2mESLp5JN1+9iDfgtiWRFGqLkCgZD6wby1kQOw@mail.gmail.com/ [3] https://lore.kernel.org/bpf/20220204185742.271030-1-song@kernel.org/ [4] https://github.com/puranjaymohan/BPF-Allocator-Bench [5] https://www.python.org/ftp/python/3.8.4/Python-3.8.4.tgz Puranjay Mohan (2): arm64: patching: implement text_poke API bpf, arm64: use bpf_prog_pack for memory management arch/arm64/include/asm/patching.h | 2 + arch/arm64/kernel/patching.c | 80 +++++++++++++++++ arch/arm64/net/bpf_jit_comp.c | 139 ++++++++++++++++++++++++------ 3 files changed, 197 insertions(+), 24 deletions(-)