All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-mm@kvack.org, Jiri Slaby <jirislaby@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Too much free memory (not used for FS cache)
Date: Thu, 15 Mar 2012 13:19:13 -0700	[thread overview]
Message-ID: <20120315131913.657d4f3d.akpm@linux-foundation.org> (raw)
In-Reply-To: <4F624C88.6050503@suse.cz>

On Thu, 15 Mar 2012 21:09:44 +0100
Jiri Slaby <jslaby@suse.cz> wrote:

> since today's -next (20120315), the MM/VFS system is very sluggish.
> Especially when committing, diffing and similar with git. I still have
> 2G of 6G of memory free. But with each commit I have to wait for git to
> fetch all data from disk.
> 
> I'm using ext4 on a raid for the partition with git kernel repository if
> that matters.
> 
> Any idea what that could be?

The last mm->next update was March 5th so it won't be from stuff in the
-mm queue.

Are you sure it's reclaim-related?  Perhaps something in the IO system
got slow?




--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-mm@kvack.org, Jiri Slaby <jirislaby@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Too much free memory (not used for FS cache)
Date: Thu, 15 Mar 2012 13:19:13 -0700	[thread overview]
Message-ID: <20120315131913.657d4f3d.akpm@linux-foundation.org> (raw)
In-Reply-To: <4F624C88.6050503@suse.cz>

On Thu, 15 Mar 2012 21:09:44 +0100
Jiri Slaby <jslaby@suse.cz> wrote:

> since today's -next (20120315), the MM/VFS system is very sluggish.
> Especially when committing, diffing and similar with git. I still have
> 2G of 6G of memory free. But with each commit I have to wait for git to
> fetch all data from disk.
> 
> I'm using ext4 on a raid for the partition with git kernel repository if
> that matters.
> 
> Any idea what that could be?

The last mm->next update was March 5th so it won't be from stuff in the
-mm queue.

Are you sure it's reclaim-related?  Perhaps something in the IO system
got slow?





  parent reply	other threads:[~2012-03-15 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 20:09 Too much free memory (not used for FS cache) Jiri Slaby
2012-03-15 20:15 ` Jiri Slaby
2012-03-15 20:15   ` Jiri Slaby
2012-03-15 20:19 ` Andrew Morton [this message]
2012-03-15 20:19   ` Andrew Morton

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=20120315131913.657d4f3d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.