get_swap_page():delay update swap_list.next
Quoted 4 lines · On Mon, 19 Oct 2009 you wrote:
If
scan_swap_map()successed in current si, there is no need to update swap_list.next.Soget_swap_pagenext time called can start search from the lastswap_info(which still have free slots).
No, I think you'll find that's mistaken. It is intended behaviour that allocating from two swap areas of the same priority will alternate between them page by page (or cycle around three or more of the same priority) - a kind of poor man's striping.
You may think that's silly, and not want that behaviour: in which case assign different priorities to those swap areas, and it will then behave like you were changing the same priority case to behave. So there is no reason to make your change.
Hugh
[I apologize for breaking the threading on your mail: I've been caught by surprise to find myself unable to reply in the usual way.]
Get 50% off Norton Security- http://www.tiscali.co.uk/securepc
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>