lkml.org 
[lkml]   [2002]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: invalidate_inode_pages in 2.5.32/3
Rik van Riel wrote:
>
> On Thu, 12 Sep 2002, Andrew Morton wrote:
>
> > Well the lazy invalidation would be OK - defer that to the next
> > userspace access,
>
> I think I have an idea on how to do that, here's some pseudocode:
>
> invalidate_page(struct page * page) {
> SetPageInvalidated(page);
> rmap_lock(page);
> for_each_pte(pte, page) {
> make pte PROT_NONE;
> flush TLBs for this virtual address;
> }
> rmap_unlock(page);
> }
>
> And in the page fault path:
>
> if (pte_protection(pte) == PROT_NONE && PageInvalidated(pte_page_pte)) {
> clear_pte(ptep);
> page_cache_release(page);
> mm->rss--;
> }
>

That's the bottom-up approach. The top-down (vmtruncate) approach
would also work, if the locking is suitable.

Look, idunnoigiveup. Like scsi and USB, NFS is a black hole
where akpms fear to tread. I think I'll sulk until someone
explains why this work has to be performed in the context of
a process which cannot do it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.218 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site