It works as expected. Doesn't lockup the box however swapoff keeps burning
the CPU cycles. It took 4 1/2 minutes to swapoff about 256MB of swap
content. Shutdown took just as long. I was hoping that shutdown would
kill the swapoff process but it doesn't. It just hangs there. Shutdown
is the common case. Therefore, swapoff needs to be optimized for
You could imagine users frustration waiting for a shutdown when there are
gigabytes in the swap.
So to summarize, schedule patch is better than nothing but falls far short.
I would put it in 2.4.6. Read on.
The problem is with the try_to_unuse() algorithm which is very inefficient.
I searched the linux-mm archives and Tweedie was on to this. This is what
he wrote: "it is much cheaper to find a swap entry for a given page than
to find the swap cache page for a given swap entry." And he posted a
His patch is in the Redhat 7.1 kernel 2.4.2-2 and not in 2.4.5.
But in any case I believe the patch will not work as expected.
It seems to me that he is calling the function check_orphaned_swap(page)
in the wrong place. He is calling the function while scanning the
active_list in refill_inactive_scan(). The problem with that is if you
60 seconds or longer the orphaned swap pages will move from active
to inactive lists. Therefore the function will miss the orphans in inactive
lists. Any comments?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/