[Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem

Andy Lutomirski luto at amacapital.net
Wed Jun 11 20:15:52 UTC 2014

On Wed, Jun 11, 2014 at 12:03 PM, Christoph Lameter <cl at gentwo.org> wrote:
> 3. Allocation "Zones". These are problematic because the zones often do
> not reflect the capabilities of devices to allocate in certain ranges.
> They are used for other purposes like MOVABLE pages but then the pages are
> not really movable because they are pinnned for other reasons. Argh.

What if you just couldn't sleep while you have a MOVABLE page pinned?
Or what if you had to pin it and provide a callback to forcibly unpin
it?  This would complicate direct IO and such, but it would make
movable pages really movable.  It would also solve an annoyance with
the sealing thing: the sealing code wants to take writable pages and
make them really readonly.  This interacts very badly with existing

We have IOMMU in many cases.  Would it be so bad to say that direct IO
is only really direct if there's an IOMMU?


More information about the Ksummit-discuss mailing list