Gennaro Cimmino
3b2bc55dcb
The transmit path frees a TX skb only when its descriptor slot is reused, RTETH_TX_RING_SIZE transmissions later. Until then the skb stays charged to the sending socket's send buffer. With standard frames the pinned amount is negligible, but with jumbo frames a handful of completed transmissions is enough to exhaust the sender's budget: eight ~9k echo replies exceed the kernel ICMP socket limit of 2 * SKB_TRUESIZE(64 * 1024), after which the stack drops every further reply of any size (Icmp OutErrors) until unrelated transmissions happen to recycle the slots. Observed on the Hasivo S1100W-8XGT-SE (RTL9303) as a total ICMP blackout setting in after exactly eight jumbo echo replies, healed by any sixteen device-originated frames. Track monotonic send/clean counters in the driver-private ring info (their difference is the number of unreleased skbs, their low bits the ring slots), and release the contiguous completed run at the start of the RX poll, before the received packets are processed, so replies generated while handling the poll always find their send budget released. The walk runs under the TX queue lock the transmit path already holds, stops at the first descriptor the hardware still owns, and is skipped entirely - no lock taken, no access to the uncached descriptor memory - while nothing is pending. The transmit path reuses the same walk for the ring-wrap case instead of its old per-slot cleanup, and stopped or watchdog-frozen queues are left to the rteth_tx_timeout() recovery, which keeps releasing every buffer itself. Assisted-by: Claude:claude-fable-5 Signed-off-by: Gennaro Cimmino <gcimmino@rayonra.net> Link: https://github.com/openwrt/openwrt/pull/24406 Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.8+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0