#8466: VM caches aren't resized in some cases when cutting areas -----------------------------+----------------------------- Reporter: hamish | Owner: bonefish Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/Development Resolution: | Keywords: kernel vm cache Blocked By: | Blocking: Has a Patch: 1 | Platform: All -----------------------------+----------------------------- Comment (by hamish): Replying to [comment:3 bonefish]: > I don't see what would speak against iterating through the other cache's page tree. Indeed, I didn't realise that the page tree was a public member. This patch depends on my patch in #8233. RE your comment there about guard sizes and cache resizing, I'm not sure quite what would be the expected behaviour in this case. Should the guard size be preserved after resizing, or should the guard be resized to prevent previously accessible pages becoming guarded? So I added a `VMAnonymous(NoSwap)Cache::SetGuardSize()` to let the caller decide what's best for them. -- Ticket URL: <http://dev.haiku-os.org/ticket/8466#comment:5> Haiku <http://dev.haiku-os.org> Haiku - the operating system.