> By the way, while we're talking of remove_exclusive_swap_page: > a more functional issue I sometimes wonder about, why don't we > remove_exclusive_swap_page on write fault? Keeping the swap slot > is valuable if read fault, but once the page is dirtied, wouldn't > it usually be better to free that slot and allocate another later?
Avoiding swap fragmentation is one reason to leave it allocated. So you can swapin/swapout/swapin/swapout always in the same place on disk as long as there's plenty of swap still available. I'm not sure how much speedup this provides, but certainly it makes sense. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/