Re: 230-objrmap fixes for 2.6.3-mjb2

From: Dave McCracken
Date: Wed Mar 03 2004 - 13:45:56 EST



--On Wednesday, March 03, 2004 19:39:01 +0100 Andrea Arcangeli
<andrea@xxxxxxx> wrote:

>> What we've actually discussed before was more along the lines of
>> PG_locked to match VM_LOCKED, but the main idea was to be able to skip
>> over ineligible pages without having ot look up their mappings during
>> pageout.
>
> I'm not very excited using PG_locked for that, that doesn't only mean
> "unswappable", it means also that the page is under I/O (or uner some
> other operation that needs serialization like unmapping the page) which
> is quite a different concept from VM_LOCKED. a wait_on_page would
> deadlock on such a PG_locked page, while wait_on_page on a page of a
> mlocked vma doesn't normally deadlock.
>
> But I see what you want to do here, and PG_reserved would be too much
> for that since it changes the semantics for cow and free_pages, but
> PG_locked doesn't look good enough either, the VM_LOCKED and PG_locked
> concept is quite different, PG_reserved and VM_RESERVED is quite close
> instead (except for the page->count accounting).

Sorry, I misspoke. I didn't mean the current PG_locked. I meant a new
flag, or more probably a counter, that represents all the VM_LOCKED regions
a page is in.

Dave McCracken

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/