linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Valdis.Kletnieks@vt.edu
Cc: Jiri Slaby <jirislaby@gmail.com>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: kswapd0: excessive CPU usage
Date: Fri, 12 Oct 2012 00:08:13 +0200	[thread overview]
Message-ID: <5077434D.7080008@suse.cz> (raw)
In-Reply-To: <119175.1349979570@turing-police.cc.vt.edu>

On 10/11/2012 08:19 PM, Valdis.Kletnieks@vt.edu wrote:
> # zgrep COMPAC /proc/config.gz
> CONFIG_COMPACTION=y
> 
> Hope that tells you something useful.

It just supports my another theory. This seems to fix it for me:
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -1830,8 +1830,8 @@ static inline bool should_continue_reclaim(struct
lruvec *lruvec,
         */
        pages_for_compaction = (2UL << sc->order);

-       pages_for_compaction = scale_for_compaction(pages_for_compaction,
-                                                   lruvec, sc);
+/*     pages_for_compaction = scale_for_compaction(pages_for_compaction,
+                                                   lruvec, sc);*/
        inactive_lru_pages = get_lru_size(lruvec, LRU_INACTIVE_FILE);
        if (nr_swap_pages > 0)
                inactive_lru_pages += get_lru_size(lruvec,
LRU_INACTIVE_ANON);

And for you?

(It's an effective revert of "mm: vmscan: scale number of pages
reclaimed by reclaim/compaction based on failures".)

regards,
-- 
js
suse labs

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

  reply	other threads:[~2012-10-11 22:08 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11  8:52 kswapd0: wxcessive CPU usage Jiri Slaby
2012-10-11 13:44 ` Valdis.Kletnieks
2012-10-11 15:34   ` Jiri Slaby
2012-10-11 17:56     ` Valdis.Kletnieks
2012-10-11 17:59       ` Jiri Slaby
2012-10-11 18:19         ` Valdis.Kletnieks
2012-10-11 22:08           ` Jiri Slaby [this message]
2012-10-12 12:37             ` kswapd0: excessive " Jiri Slaby
2012-10-12 13:57               ` Mel Gorman
2012-10-15  9:54                 ` Jiri Slaby
2012-10-15 11:09                   ` Mel Gorman
2012-10-29 10:52                     ` Thorsten Leemhuis
2012-10-30 19:18                       ` Mel Gorman
2012-10-31 11:25                         ` Thorsten Leemhuis
2012-10-31 15:04                           ` Mel Gorman
2012-11-04 16:36                         ` Rik van Riel
2012-11-02 10:44                     ` Zdenek Kabelac
2012-11-02 10:53                       ` Jiri Slaby
2012-11-02 19:45                         ` Jiri Slaby
2012-11-04 11:26                           ` Zdenek Kabelac
2012-11-05 14:24                           ` [PATCH] Revert "mm: vmscan: scale number of pages reclaimed by reclaim/compaction based on failures" Mel Gorman
2012-11-06 10:15                             ` Johannes Hirte
2012-11-09  8:36                               ` Mel Gorman
2012-11-14 21:43                                 ` Johannes Hirte
2012-11-09  9:12                             ` Mel Gorman
2012-11-09  4:22                           ` kswapd0: excessive CPU usage Seth Jennings
2012-11-09  8:07                             ` Zdenek Kabelac
2012-11-09  9:06                               ` Mel Gorman
2012-11-11  9:13                                 ` Zdenek Kabelac
2012-11-12 11:37                                   ` [PATCH] Revert "mm: remove __GFP_NO_KSWAPD" Mel Gorman
2012-11-16 19:14                                     ` Josh Boyer
2012-11-16 19:51                                       ` Andrew Morton
2012-11-20  1:43                                         ` Valdis.Kletnieks
2012-11-16 20:06                                       ` Mel Gorman
2012-11-20 15:38                                         ` Josh Boyer
2012-11-20 16:13                                           ` Bruno Wolff III
2012-11-20 17:43                                           ` Thorsten Leemhuis
2012-11-23 15:20                                             ` Thorsten Leemhuis
2012-11-27 11:12                                               ` Mel Gorman
2012-11-21 15:08                                           ` Mel Gorman
2012-11-20  9:18                                     ` Glauber Costa
2012-11-20 20:18                                       ` Andrew Morton
2012-11-21  8:30                                         ` Glauber Costa
2012-11-12 12:19                                   ` kswapd0: excessive CPU usage Mel Gorman
2012-11-12 13:13                                     ` Zdenek Kabelac
2012-11-12 13:31                                       ` Mel Gorman
2012-11-12 14:50                                         ` Zdenek Kabelac
2012-11-18 19:00                                         ` Zdenek Kabelac
2012-11-18 19:07                                           ` Jiri Slaby
2012-11-09  8:40                             ` Mel Gorman
2012-10-11 22:14 ` kswapd0: wxcessive " Andrew Morton
2012-10-11 22:26   ` Jiri Slaby

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=5077434D.7080008@suse.cz \
    --to=jslaby@suse.cz \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).