ZFS swap space can trigger OOM much earlier.
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
Comment Actions
Two suggestions.
sbin/swapon/swapon.8 | ||
---|---|---|
211 | killing what? I would insert "(random?) processes" here. |
sbin/swapon/swapon.8 | ||
---|---|---|
208 | It does not matter how much memory is required for write. What matter is that each write requires allocation of memory. |
Comment Actions
If the VM high watermark levels are tweaked, OOM from ZFS on swap can be entirely avoided. Don't know if this is relevant?
Comment Actions
Any updates on this one? The suggested changes don't seem too difficult to me.
@ota_j.email.ne.jp are you interested in finishing this?
Comment Actions
.Sh NOTE ZVOLs are discouraged for use as swap devices, because ZFS needs to allocate memory in order to write, which may not be possible while the system is under memory pressure. In other words, ZFS needs memory to make memory available. ZFS swap files are discouraged for the same reason.
Comment Actions
Upstream:
I opened this PR in response to https://github.com/openzfs/zfs/issues/7734#issuecomment-1510451126; I wasn't aware of D22150 at the time.