> > The kswapd logic is almost completely redone. Basically,
> > kswapd tries (free_pages_high - nr_free_pages) times to
> > free a page, but when memory becomes tighter, the number
> > of tries become even higher.
>
> Is the explicit call of run_task_queue(&tq_disk) really needed?
> Maybe setting of the __GFP_WAIT flag would work in the same manner:
>
> gfp_mask = __GFP_IO;
> if (atomic_read(&nr_async_pages) >= SWAP_CLUSTER_MAX)
> gfp_mask |= __GFP_WAIT;
Wouldn't that just mean that the pages that are
swapped out from now on will be done synchronously?
What I wanted kswapd to do, was to select SWAP_CLUSTER_MAX
pages and swap them out in _one_ I/O operation. Because
this should save head movement, it might give us an improvement
over syncing each swapped page seperately.
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu