[$] Improving the per-CPU memory allocator
The 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit addressed performance issues with the kernel's per-CPU memory allocator. Harry Yoo led discussions on improving allocation and initialization processes, highlighting scalability and initialization cost concerns. Proposed solutions included dual-mode per-CPU counters and integrating the allocator with the slab allocator.
- ▪Harry Yoo led a session on improving the per-CPU memory allocator at the 2026 Linux Summit.
- ▪The current allocator has scalability issues due to a global lock and expensive initialization costs.
- ▪Proposals for improvement include dual-mode counters and closer integration with the slab allocator.
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/1072840/ |
| Publication time | Tue, 19 May 2026 13:27:28 +0000 |
| Retrieval time | 2026-05-19T13:29:57.664Z |
| Last seen | 2026-05-19T13:30:00.251Z |
| 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 | NXK-I8gbzbCb |
| 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
Ready to give LWN a try? With a subscription to LWN, you can stay current with what is happening in the Linux and free-software community and take advantage of subscriber-only site features. We are pleased to offer you a free trial subscription, no credit card required, so that you can see for yourself. Please, join us! By Jonathan CorbetMay 19, 2026 LSFMM+BPF There are many places in the kernel where performance can be improved by using per-CPU data. But, as it turns out, the kernel's allocator for per-CPU data has some performance problems of its own. Harry Yoo led a session in the memory-management track of the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit to explore ways to address those problems and accelerate the allocation and initialization of per-CPU data.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at LWN.net (Linux Weekly News).