linux-kernel - Re: [PATCH -mm 2/2] mm: kswapd carefully invoke compaction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHGf_=qJv99TbF2eNosbeHU5pzk2e3mDer0u2U+EsXdf2p5_Aw@mail.gmail.com>
Date:	Wed, 11 Jan 2012 14:57:25 -0500
From:	KOSAKI Motohiro <kosaki.motohiro@...il.com>
To:	Rik van Riel <riel@...hat.com>
Cc:	linux-mm@...ck.org, aarcange@...hat.com,
	linux-kernel@...r.kernel.org, Mel Gorman <mel@....ul.ie>,
	akpm@...ux-foundation.org, Johannes Weiner <hannes@...xchg.org>,
	hughd@...gle.com
Subject: Re: [PATCH -mm 2/2] mm: kswapd carefully invoke compaction

> I believe we do need some background compaction, especially
> to help allocations from network interrupts.

I completely agree.


> If you believe the compaction is better done from some
> other thread, I guess we could do that, but truthfully, if
> kswapd spends a lot of time doing compaction, I made a
> mistake somewhere :)

I don't have much experience of compaction on real production systems.
but I have a few bad experience of background lumpy reclaim. If much
network allocation is happen when kswapd get stucked large order lumpy
reclaim, kswapd can't work for making order-0 job.it was bad. I'm only
worry about similar issue will occur.

But, ok, we can fix it when we actually observed such thing. So,
please go ahead.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/