FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2025-08-23T04:58:40Z 2025-08-23T04:58:40Z ShengYi Hung aokblast@FreeBSD.org 2025-08-21T08:27:06Z urn:sha1:8a847947153e60d812852e5c02de93997b2d3038 Multiple Makefile miss opt_*.h and *_if.h header file. We fix it by running make in sys/modules to build all modules. Approved by: lwhsu (mentor), markj (mentor) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D52062 2023-08-16T17:54:58Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:58Z urn:sha1:031beb4e239bfce798af17f5fe8dba8bcaf13d99 Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ 2022-09-26T19:34:01Z Bjoern A. Zeeb bz@FreeBSD.org 2022-09-23T21:18:45Z urn:sha1:514fb3872166a361faa81d89909f65913e90b1b2 While for in-kernel we already have LINUXKPI_INCLUDES in kern.pre.mk for kmod builds we've not had a common define to use leading to various spellings of include paths. In order for the include list to be expanded more easily in the future, e.g., adding the "dummy" includes (for all) and to harmonize code, duplicate LINUXKPI_INCLUDES to kmod.mk and use it for all module Makefiles. MFC after: 1 week Reviewed by: hselasky Differential Revision: https://reviews.freebsd.org/D36683 2022-02-01T15:21:17Z Hans Petter Selasky hselasky@FreeBSD.org 2022-02-01T15:20:16Z urn:sha1:84d7b8e75f251ee5b33a92c3cd268396809b015b TLS RX support is modeled after TLS TX support. The basic structures and layouts are almost identical, except that the send tag created filters RX traffic and not TX traffic. The TLS RX tag keeps track of past TLS records up to a certain limit, approximately 1 Gbyte of TCP data. TLS records of same length are joined into a single database record. Regularly the HW is queried for TLS RX progress information. The TCP sequence number gotten from the HW is then matches against the database of TLS TCP sequence number records and lengths. If a match is found a static params WQE is queued on the IQ and the hardware should immediately resume decrypting TLS data until the next non-sequential TCP packet arrives. Offloading TLS RX data is supported for untagged, prio-tagged, and regular VLAN traffic. MFC after: 1 week Sponsored by: NVIDIA Networking 2022-02-01T15:21:15Z Hans Petter Selasky hselasky@FreeBSD.org 2022-02-01T15:20:09Z urn:sha1:694263572f1bdf545199fcfb0853b93eb0dd0644 Internal send queues are regular sendqueues which are reserved for WQE commands towards the hardware and firmware. These queues typically carry resync information for ongoing TLS RX connections and when changing schedule queues for rate limited connections. The internal queue, IQ, code is more or less a stripped down copy of the existing SQ managing code with exception of: 1) An optional single segment memory buffer which can be read or written as a whole by the hardware, may be provided. 2) An optional completion callback for all transmit operations, may be provided. 3) Does not support mbufs. MFC after: 1 week Sponsored by: NVIDIA Networking 2021-07-28T11:28:29Z Hans Petter Selasky hselasky@FreeBSD.org 2021-06-16T13:02:00Z urn:sha1:b633e08c705fe43180567eae26923d6f6f98c8d9 Overview: This is the first stage of a RDMA stack upgrade introducing kernel changes only based on Linux 5.7-rc1. This patch is based on about four main areas of work: - Update of the IB uobjects system: - The memory holding so-called AH, CQ, PD, SRQ and UCONTEXT objects is now managed by ibcore. This also require some changes in the kernel verbs API. The updated verbs changes are typically about initialize and deinitialize objects, and remove allocation and free of memory. - Update of the uverbs IOCTL framework: - The parsing and handling of user-space commands has been completely refactored to integrate with the updated IB uobjects system. - Various changes and updates to the generic uverbs interfaces in device drivers including the new uAPI surface. - The mlx5_ib_devx.c in mlx5ib and related mlx5 core changes. Dependencies: - The mlx4ib driver code has been updated with the minimum changes needed. - The mlx5ib driver code has been updated with the minimum changes needed including DV support. Compatibility: - All user-space facing APIs are backwards compatible after this change. - All kernel-space facing RDMA APIs are backwards compatible after this change, with exception of ib_create_ah() and ib_destroy_ah() which takes a new flag. - The "ib_device_ops" structure exist, but only contains the driver ID and some structure sizes. Differences from Linux: - Infiniband drivers must use the INIT_IB_DEVICE_OPS() macro to set the sizes needed for allocating various IB objects, when adding IB device instances. Security: - PRIV_NET_RAW is needed to use raw ethernet transmit features. - PRIV_DRIVER is needed to use other privileged operations. Based on upstream Linux, Torvalds (5.7-rc1): 8632e9b5645bbc2331d21d892b0d6961c1a08429 MFC after: 1 week Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D31149 Sponsored by: NVIDIA Networking 2020-03-20T21:06:58Z Konstantin Belousov kib@FreeBSD.org 2020-03-20T21:06:58Z urn:sha1:15fe2513996eaa8857fcf66a632814b5f9374b03 Centralize the list of generated files required by linuxkpi consumers, into the common variable. This way, consumers that use the variable are insulated from possible changes in the list. Reviewed by: hselasky, imp Sponsored by: Mellanox Technologies MFC after: 1 week Differential revision: https://reviews.freebsd.org/D24137 2020-03-18T22:09:16Z Konstantin Belousov kib@FreeBSD.org 2020-03-18T22:09:16Z urn:sha1:84b3c4547afa496b37e86c5e649e99237c8afc6e Sponsored by: Mellanox Technologies MFC after: 2 weeks 2019-12-06T15:36:32Z Hans Petter Selasky hselasky@FreeBSD.org 2019-12-06T15:36:32Z urn:sha1:7272f9cd774c4643a33d92db6cc3e1641ceab5c9 ConnectX-6 DX. Currently TLS v1.2 and v1.3 with AES 128/256 crypto over TCP/IP (v4 and v6) is supported. A per PCI device UMA zone is used to manage the memory of the send tags. To optimize performance some crypto contexts may be cached by the UMA zone, until the UMA zone finishes the memory of the given send tag. An asynchronous task is used manage setup of the send tags towards the firmware. Most importantly setting the AES 128/256 bit pre-shared keys for the crypto context. Updating the state of the AES crypto engine and encrypting data, is all done in the fast path. Each send tag tracks the TCP sequence number in order to detect non-contiguous blocks of data, which may require a dump of prior unencrypted data, to restore the crypto state prior to wire transmission. Statistics counters have been added to count the amount of TLS data transmitted in total, and the amount of TLS data which has been dumped prior to transmission. When non-contiguous TCP sequence numbers are detected, the software needs to dump the beginning of the current TLS record up until the point of retransmission. All TLS counters utilize the counter(9) API. In order to enable hardware TLS offload the following sysctls must be set: kern.ipc.mb_use_ext_pgs=1 kern.ipc.tls.ifnet.permitted=1 kern.ipc.tls.enable=1 Sponsored by: Mellanox Technologies 2019-10-02T10:05:34Z Hans Petter Selasky hselasky@FreeBSD.org 2019-10-02T10:05:34Z urn:sha1:c28ef249180e02ae7d194d6b131027e244bea5a5 Submitted by: kib@ MFC after: 3 days Sponsored by: Mellanox Technologies