WeSearch

[$] Custom page-cache policies with BPF

·6 min read · 0 reactions · 0 comments · 42 views
TL;DR · WeSearch summary

At the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit, Tal Zussman discussed improving the kernel's page cache to better serve specific workloads. He highlighted the limitations of current eviction policies, particularly for applications with mixed workloads, such as financial databases. Zussman proposed a new feature called cache_ext, which would allow user-defined page-cache policies to be implemented via BPF programs without requiring kernel changes.

Key facts
About this source

LWN.net (Linux Weekly News) files mainly under tech. We currently carry 86 of its stories.

Original article
LWN.net (Linux Weekly News)
Read full at LWN.net (Linux Weekly News) →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

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 publisherLWN.net (Linux Weekly News)
Canonical URLhttps://lwn.net/Articles/1073103/
Publication timeFri, 22 May 2026 14:37:10 +0000
Retrieval time2026-05-22T14:42:02.370Z
Last seen2026-05-22T14:42:03.752Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterFefPvxoDz5Hz
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

Did you know...? LWN.net is a subscriber-supported publication; we rely on subscribers to keep the entire operation going. Please help out by buying a subscription and keeping LWN on the net. By Jonathan CorbetMay 22, 2026 LSFMM+BPF The kernel's page cache is charged with maintaining pages (or, more correctly, folios) containing copies of data from files in the filesystem; its performance has a big effect on the performance of the system as a whole. One of the key decisions the kernel must make is when to evict folios from the page cache. At the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit, Tal Zussman ran a memory-management-track session on how the page cache could be better customized for specific workloads.

Excerpt limited to ~120 words for fair-use compliance. The full article is at LWN.net (Linux Weekly News).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments