From: Krishna Reddy <vdumpa@nvidia.com>
To: Lock Free <atomiclong64@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: RE: Greedy kswapd reclaim behavior
Date: Wed, 11 Mar 2015 00:02:15 +0000 [thread overview]
Message-ID: <fe129e5a96d84f279693d0d4d764425c@HQMAIL108.nvidia.com> (raw)
In-Reply-To: <loom.20150310T211234-554@post.gmane.org>
> Is it expected that kswapd reclaims significantly more pages than the high
> watermark?
What zones(DMA, DMA32, Normal, etc.) do you have in the system? You can check
under /proc/zoneinfo.
Each zone has its own Kswapd thread. Whenever a zone's free memory
is less than low watermark, Kswapd thread of that zone is woke up and it tries
to reclaim memory till the zone's high watermark is reached. During reclaim,
pages are swapped out from the zone's lru lists and various caches in kernel.
only swap out from lru lists ensure that pages released belong to the zone,
which kswapd is running for.
Caches shrinking doesn't necessarily release the pages of a particular zone.
The memory reclaimed from caches can belong to other zones and the kswapd
doesn't sleep based on total free memory available.
You need to check the free memory available in the zone, which kswapd is running for.
-Krishna Reddy
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-03-11 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 3:15 Lock Free
2015-03-10 20:18 ` Lock Free
2015-03-11 0:02 ` Krishna Reddy [this message]
2015-03-11 5:39 ` Lock Free
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe129e5a96d84f279693d0d4d764425c@HQMAIL108.nvidia.com \
--to=vdumpa@nvidia.com \
--cc=atomiclong64@gmail.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox