linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Will Huck <will.huckk@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Raymond Jennings <shentino@gmail.com>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: Swap defragging
Date: Wed, 13 Mar 2013 09:31:30 +0800	[thread overview]
Message-ID: <513FD6F2.5060804@gmail.com> (raw)
In-Reply-To: <20130312165247.GB1953@cmpxchg.org>

Hi Johannes,
On 03/13/2013 12:52 AM, Johannes Weiner wrote:
> On Sat, Mar 09, 2013 at 10:00:37AM +0800, Will Huck wrote:
>> Hi Johannes,
>> On 03/08/2013 10:35 AM, Johannes Weiner wrote:
>>> On Thu, Mar 07, 2013 at 06:07:23PM -0800, Raymond Jennings wrote:
>>>> Just a two cent question, but is there any merit to having the kernel
>>>> defragment swap space?
>>> That is a good question.
>>>
>>> Swap does fragment quite a bit, and there are several reasons for
>>> that.
>> Are there any tools to test and monitor swap subsystem and page
>> reclaim subsystem?

pgscan_kswapd_dma 0
pgscan_kswapd_dma32 0
pgscan_kswapd_normal 0
pgscan_kswapd_movable 0
pgscan_direct_dma 0
pgscan_direct_dma32 0
pgscan_direct_normal 0
pgscan_direct_movable 0
pgscan_direct_throttle 0
zone_reclaim_failed 0
pginodesteal 0
slabs_scanned 328704

slab cache is scaned but file-backed/swap-backed pages are not scanned, why?

> seekwatcher is great to see the IO patterns.  Anything that uses
> anonymous memory can test swap: a java job, multiplying matrixes,
> kernel builds etc.  I mostly log /proc/vmstat by taking snapshots at a
> regular interval during the workload, then plot and visually correlate
> the swapin/swapout counters with the individual LRU sizes, page fault
> rate, what have you, to get a feeling for what it's doing.

--
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>

  parent reply	other threads:[~2013-03-13  1:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  2:07 Swap defragging Raymond Jennings
2013-03-08  2:35 ` Johannes Weiner
2013-03-08  3:01   ` Raymond Jennings
2013-03-09  2:00   ` Will Huck
2013-03-12 16:52     ` Johannes Weiner
2013-03-13  0:46       ` Will Huck
2013-03-13  1:31       ` Will Huck [this message]
2013-03-11  2:54   ` Ric Mason
2013-03-12 16:53     ` Johannes Weiner
2013-03-11  3:11   ` Simon Jeons
2013-03-12 17:03     ` Johannes Weiner
2013-03-11  3:16   ` Jaegeuk Hanse
2013-03-12 17:08     ` Johannes Weiner
2013-03-13  3:47       ` Jaegeuk Hanse
2013-03-11  6:24   ` Will Huck

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=513FD6F2.5060804@gmail.com \
    --to=will.huckk@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=shentino@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).