Lesson plan

Zswap

zswap is a Linux kernel feature that provides a compressed write-back cache for swapped pages, as a form of virtual memory compression. Instead of moving memory pages to a swap device when they are to be swapped out, zswap compresses them and then stores them in a memory pool dynamically allocated in the system RAM. This way, writeback to the actual swap device is deferred or even completely avoided, resulting in a significantly reduced I/O load for systems that require swapping; the tradeoff is the need for additional CPU cycles to perform the compression. As a result of reduced I/O, zswap offers advantages to various devices that use flash-based storage, including embedded devices, netbooks and similar low-end hardware devices, as well as to other devices that use solid-state drives (SSDs) for storage. Flash memory has a limited lifespan due to its nature, so avoiding using it as swap space extends its lifespan.

Back to article

Article summary

zswap is a Linux kernel feature that provides a compressed write-back cache for swapped pages, as a form of virtual memory compression. Instead of moving memory pages to a swap device when they are to be swapped out, zswap compresses them and then stores them in a memory pool dynamically allocated in the system RAM. This way, writeback to the actual swap device is deferred or even completely avoided, resulting in a significantly reduced I/O load for systems that require swapping; the tradeoff is the need for additional CPU cycles to perform the compression. As a result of reduced I/O, zswap offers advantages to various devices that use flash-based storage, including embedded devices, netbooks and similar low-end hardware devices, as well as to other devices that use solid-state drives (SSDs) for storage. Flash memory has a limited lifespan due to its nature, so avoiding using it as swap space extends its lifespan.

Key claims

  1. release date: 2025-12-01 — source: Wikipedia, revision 1377670826, retrieved 2026-10-20 · confidence 0.95
  2. release date: 2013-09-02 — source: Wikipedia, revision 1377670826, retrieved 2026-10-20 · confidence 0.95
  3. release date: 2014-06-08 — source: Wikipedia, revision 1377670826, retrieved 2026-10-20 · confidence 0.95
  4. release date: 2024-03-11 — source: Wikipedia, revision 1377670826, retrieved 2026-10-20 · confidence 0.95
  5. release date: 2025-12-01 — source: Wikipedia, revision 1377670826, retrieved 2026-10-20 · confidence 0.95

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. The record states that the release date is "2025-12-01". What evidence would count against this claim?
  3. The record states that the release date is "2013-09-02". What evidence would count against this claim?
  4. The record states that the release date is "2014-06-08". What evidence would count against this claim?
  5. The record states that the release date is "2024-03-11". What evidence would count against this claim?
  6. The record states that the release date is "2025-12-01". What evidence would count against this claim?
  7. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  8. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.