On Wed, Jul 25, 2012 at 02:51:19PM -0400, Rik van Riel wrote:
> Turns out I missed two spots where __GFP_NO_KSWAPD is used.
>
> The removal from the trace code is obvious, since the flag
> got removed there is no need to print it.
>
> For mtdcore.c, now that memory compaction has been fixed,
> we
Turns out I missed two spots where __GFP_NO_KSWAPD is used.
The removal from the trace code is obvious, since the flag
got removed there is no need to print it.
For mtdcore.c, now that memory compaction has been fixed,
we should no longer see large swap storms from an attempt
to allocate a large
On 07/24/2012 07:34 PM, Minchan Kim wrote:
Hi Rik,
On Tue, Jul 24, 2012 at 11:12:22AM -0400, Rik van Riel wrote:
When transparent huge pages were introduced, memory compaction and
swap storms were an issue, and the kernel had to be careful to not
make THP allocations cause pageout or compaction
Hi Rik,
On Tue, Jul 24, 2012 at 11:12:22AM -0400, Rik van Riel wrote:
> When transparent huge pages were introduced, memory compaction and
> swap storms were an issue, and the kernel had to be careful to not
> make THP allocations cause pageout or compaction.
>
> Now that we have working compacti
When transparent huge pages were introduced, memory compaction and
swap storms were an issue, and the kernel had to be careful to not
make THP allocations cause pageout or compaction.
Now that we have working compaction deferral, kswapd is smart enough
to invoke compaction and the quadratic behavi
5 matches
Mail list logo