--- Dave Hansen <haveblue _at_ us.ibm.com> wrote: > The "work until we get interrupted and restart if > something changes > state" approach is very, very common. Can you give > some more examples > of just how a page fault would ruin the defrag > process? > What I mean to say is that if we have identified some pages for movement, & we get preempted, the pages identified as movable may not remain movable any more when we are rescheduled. We are left with the task of identifying new movable pages. -Alok __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: Active Memory Defragmentation: Our implementation & problemsRichard B. Johnson
- Re: Active Memory Defragmentation: Our implementation & problemsDave Hansen
- Prev by Date: Re: fb.h header fix.
- Next by Date: Re: Active Memory Defragmentation: Our implementation & problems
- Previous by thread: Re: Active Memory Defragmentation: Our implementation & problems
- Next by thread: Re: Active Memory Defragmentation: Our implementation & problems
- Indexes:[Main][Thread]