FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F14.3 2023-08-16T17:54:36Z 2023-08-16T17:54:36Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:36Z urn:sha1:685dc743dc3b5645e34836464128e1c0558b404b Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ 2023-02-14T15:21:19Z Justin Hibbits jhibbits@FreeBSD.org 2023-01-12T18:38:37Z urn:sha1:e330262f34fc179ce920c16bb28ba8a1c4a73aff Reviewed by: vmaffione, zlei Sponsored by: Juniper Networks, Inc. Differential Revision: https://reviews.freebsd.org/D37814 2022-03-06T17:29:44Z Vincenzo Maffione vmaffione@FreeBSD.org 2022-03-06T17:28:44Z urn:sha1:dd6ab49a9aebb5fbb85973d9a859d24daa5e2165 The new dev.netmap.max_bridges sysctl tunable can be set in loader.conf(5) to change the default maximum number of VALE switches that can be created. Current defaults is 8. MFC after: 2 weeks 2021-04-02T07:01:20Z Vincenzo Maffione vmaffione@FreeBSD.org 2021-04-02T07:01:20Z urn:sha1:45c67e8f6b56b9744f01142747fadf291fe3fad2 No functional changes intended. 2021-03-29T16:29:01Z Vincenzo Maffione vmaffione@FreeBSD.org 2021-03-29T16:22:48Z urn:sha1:a6d768d845c173823785c71bb18b40074e7a8998 This feature enables applications to ask netmap to transmit or receive packets starting at a user-specified offset from the beginning of the netmap buffer. This is meant to ease those packet manipulation operations such as pushing or popping packet headers, that may be useful to implement software switches, routers and other packet processors. To use the feature, drivers (e.g., iflib, vtnet, etc.) must have explicit support. This change does not add support for any driver, but introduces the necessary kernel changes. However, offsets support is already included for VALE ports and pipes. 2021-01-24T21:59:02Z Vincenzo Maffione vmaffione@FreeBSD.org 2021-01-24T21:59:02Z urn:sha1:ee0005f11f2b38a714bc66b7d79832108f6fee77 Changes imported from the netmap github. 2019-10-31T21:01:34Z Vincenzo Maffione vmaffione@FreeBSD.org 2019-10-31T21:01:34Z urn:sha1:c7c780553187d5a8ccb6d17e03c43e0c6daf8ecc The valectl(4) program is used to manage vale(4) switches. Add it to the system commands so that it can be used right away. This program was previously called vale-ctl, and stored in tools/tools/netmap Reviewed by: hrs, bcr, lwhsu, kevans MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D22146 2019-02-05T12:10:48Z Vincenzo Maffione vmaffione@FreeBSD.org 2019-02-05T12:10:48Z urn:sha1:75f4f3ed51ea3eb78ed77e255845aa301b657bc4 Changelist: - Replace ND, D and RD macros with nm_prdis, nm_prinf, nm_prerr and nm_prlim, to avoid possible naming conflicts. - Add netmap_krings_mode_commit() helper function and use that to reduce code duplication. - Refactor pipes control code to export some functions that can be reused by the veth driver (on Linux) and epair(4). - Add check to reject API requests with version less than 11. - Small code refactoring for the null adapter. MFC after: 1 week 2019-01-29T10:28:50Z Vincenzo Maffione vmaffione@FreeBSD.org 2019-01-29T10:28:50Z urn:sha1:a56136a1ba97e9b7cbe914f5d9549c852620640e On sync-kloop stop, send a wake-up signal to the kloop, so that waiting for the timeout is not needed. Also, improve logging in netmap_freebsd.c. MFC after: 3 days 2018-12-05T11:57:16Z Vincenzo Maffione vmaffione@FreeBSD.org 2018-12-05T11:57:16Z urn:sha1:b6e66be22bdce2aadcf52ee6230faa1e6cd3f805 Changelist: - Replace netmap passthrough host support with a more general mechanism to call TXSYNC/RXSYNC from an in-kernel event-loop. No kernel threads are used to use this feature: the application is required to spawn a thread (or a process) and issue a SYNC_KLOOP_START (NIOCCTRL) command in the thread body. The kernel loop is executed by the ioctl implementation, which returns to userspace only when a different thread calls SYNC_KLOOP_STOP or the netmap file descriptor is closed. - Update the if_ptnet driver to cope with the new data structures, and prune all the obsolete ptnetmap code. - Add support for "null" netmap ports, useful to allocate netmap_if, netmap_ring and netmap buffers to be used by specialized applications (e.g. hypervisors). TXSYNC/RXSYNC on these ports have no effect. - Various fixes and code refactoring. Sponsored by: Sunny Valley Networks Differential Revision: https://reviews.freebsd.org/D18015