[$] Better automatic management of transparent huge pages
The 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit featured discussions on improving the management of transparent huge pages (THPs) in Linux systems. Nico Pache and David Hildenbrand explored ways to enhance THP utilization and transparency for applications. The consensus among developers is to create an automatic mechanism that optimally allocates and manages THPs based on memory usage thresholds.
- ▪Transparent huge pages (THPs) aim to enhance performance by improving translation lookaside buffer (TLB) utilization.
- ▪Nico Pache is working on making THP usage more transparent and easier for applications.
- ▪Developers discussed the need for an automatic mechanism to manage THPs based on memory usage thresholds.
LWN.net (Linux Weekly News) files mainly under tech. We currently carry 86 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | LWN.net (Linux Weekly News) |
| Canonical URL | https://lwn.net/Articles/1073407/ |
| Publication time | Tue, 26 May 2026 13:23:23 +0000 |
| Retrieval time | 2026-05-26T13:27:49.479Z |
| Last seen | 2026-05-26T13:27:51.607Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | lTN9V_j8QmrD |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
By Jonathan CorbetMay 26, 2026 LSFMM+BPF Huge pages can improve performance by increasing translation lookaside buffer (TLB) utilization and reducing memory-management overhead. Transparent huge pages (THPs) are supposed to make huge-page usage, well, transparent, Nico Pache said at the beginning of his session in the memory-management track of the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit. That transparency has never worked as well as many would like; he has been working on improvements to make it easier for applications to use huge pages on Linux systems. A following session, led by David Hildenbrand, was focused on how THPs could be taken away from processes that are not using them fully.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at LWN.net (Linux Weekly News).