All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Simon Kirby <sim@hostway.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: Free memory never fully used, swapping
Date: Wed, 24 Nov 2010 09:27:53 +0000	[thread overview]
Message-ID: <20101124092753.GS19571@csn.ul.ie> (raw)
In-Reply-To: <20101124064329.GB25170@hostway.ca>

On Tue, Nov 23, 2010 at 10:43:29PM -0800, Simon Kirby wrote:
> On Tue, Nov 23, 2010 at 10:04:03AM +0000, Mel Gorman wrote:
> 
> > On Mon, Nov 22, 2010 at 03:44:19PM -0800, Andrew Morton wrote:
> > > On Mon, 15 Nov 2010 11:52:46 -0800
> > > Simon Kirby <sim@hostway.ca> wrote:
> > > 
> > > > I noticed that CONFIG_NUMA seems to enable some more complicated
> > > > reclaiming bits and figured it might help since most stock kernels seem
> > > > to ship with it now.  This seems to have helped, but it may just be
> > > > wishful thinking.  We still see this happening, though maybe to a lesser
> > > > degree.  (The following observations are with CONFIG_NUMA enabled.)
> > > > 
> > 
> > Hi,
> > 
> > As this is a NUMA machine, what is the value of
> > /proc/sys/vm/zone_reclaim_mode ? When enabled, this reclaims memory
> > local to the node in preference to using remote nodes. For certain
> > workloads this performs better but for users that expect all of memory
> > to be used, it has surprising results.
> > 
> > If set to 1, try testing with it set to 0 and see if it makes a
> > difference. Thanks
> 
> Hi Mel,
> 
> It is set to 0.  It's an Intel EM64T...I only enabled CONFIG_NUMA since
> it seemed to enable some more complicated handling, and I figured it
> might help, but it didn't seem to.  It's also required for
> CONFIG_COMPACTION, but that is still marked experimental.
> 

I'm surprised a little that you are bringing compaction up because unless
there are high-order involved, it wouldn't make a difference. Is there
a constant source of high-order allocations in the system e.g. a network
card configured to use jumbo frames? A possible consequence of that is that
reclaim is kicking in early to free order-[2-4] pages that would prevent 100%
of memory being used.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mel@csn.ul.ie>
To: Simon Kirby <sim@hostway.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: Free memory never fully used, swapping
Date: Wed, 24 Nov 2010 09:27:53 +0000	[thread overview]
Message-ID: <20101124092753.GS19571@csn.ul.ie> (raw)
In-Reply-To: <20101124064329.GB25170@hostway.ca>

On Tue, Nov 23, 2010 at 10:43:29PM -0800, Simon Kirby wrote:
> On Tue, Nov 23, 2010 at 10:04:03AM +0000, Mel Gorman wrote:
> 
> > On Mon, Nov 22, 2010 at 03:44:19PM -0800, Andrew Morton wrote:
> > > On Mon, 15 Nov 2010 11:52:46 -0800
> > > Simon Kirby <sim@hostway.ca> wrote:
> > > 
> > > > I noticed that CONFIG_NUMA seems to enable some more complicated
> > > > reclaiming bits and figured it might help since most stock kernels seem
> > > > to ship with it now.  This seems to have helped, but it may just be
> > > > wishful thinking.  We still see this happening, though maybe to a lesser
> > > > degree.  (The following observations are with CONFIG_NUMA enabled.)
> > > > 
> > 
> > Hi,
> > 
> > As this is a NUMA machine, what is the value of
> > /proc/sys/vm/zone_reclaim_mode ? When enabled, this reclaims memory
> > local to the node in preference to using remote nodes. For certain
> > workloads this performs better but for users that expect all of memory
> > to be used, it has surprising results.
> > 
> > If set to 1, try testing with it set to 0 and see if it makes a
> > difference. Thanks
> 
> Hi Mel,
> 
> It is set to 0.  It's an Intel EM64T...I only enabled CONFIG_NUMA since
> it seemed to enable some more complicated handling, and I figured it
> might help, but it didn't seem to.  It's also required for
> CONFIG_COMPACTION, but that is still marked experimental.
> 

I'm surprised a little that you are bringing compaction up because unless
there are high-order involved, it wouldn't make a difference. Is there
a constant source of high-order allocations in the system e.g. a network
card configured to use jumbo frames? A possible consequence of that is that
reclaim is kicking in early to free order-[2-4] pages that would prevent 100%
of memory being used.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-11-24  9:28 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 19:52 Free memory never fully used, swapping Simon Kirby
2010-11-22 23:44 ` Andrew Morton
2010-11-22 23:44   ` Andrew Morton
2010-11-23  1:34   ` Simon Kirby
2010-11-23  1:34     ` Simon Kirby
2010-11-23  8:35   ` Dave Hansen
2010-11-23  8:35     ` Dave Hansen
2010-11-24  8:46     ` Simon Kirby
2010-11-24  8:46       ` Simon Kirby
2010-11-25  1:07       ` Shaohua Li
2010-11-25  1:07         ` Shaohua Li
2010-11-25  9:03         ` Simon Kirby
2010-11-25  9:03           ` Simon Kirby
2010-11-25 10:18           ` KOSAKI Motohiro
2010-11-25 10:18             ` KOSAKI Motohiro
2010-11-25 17:13             ` Simon Kirby
2010-11-25 17:13               ` Simon Kirby
2010-11-26  0:33               ` KOSAKI Motohiro
2010-11-26  0:33                 ` KOSAKI Motohiro
2010-11-25 10:51           ` KOSAKI Motohiro
2010-11-25 10:51             ` KOSAKI Motohiro
2010-11-25 16:15             ` Mel Gorman
2010-11-25 16:15               ` Mel Gorman
2010-11-26  2:00               ` Shaohua Li
2010-11-26  2:00                 ` Shaohua Li
2010-11-26  2:31                 ` KOSAKI Motohiro
2010-11-26  2:31                   ` KOSAKI Motohiro
2010-11-26  2:40                   ` Shaohua Li
2010-11-26  2:40                     ` Shaohua Li
2010-11-26  9:18                     ` KOSAKI Motohiro
2010-11-26  9:18                       ` KOSAKI Motohiro
2010-11-29  1:03                       ` Shaohua Li
2010-11-29  1:03                         ` Shaohua Li
2010-11-29  1:13                         ` KOSAKI Motohiro
2010-11-29  1:13                           ` KOSAKI Motohiro
2010-11-26  0:07             ` KOSAKI Motohiro
2010-11-26  0:07               ` KOSAKI Motohiro
2010-11-25 16:12           ` Mel Gorman
2010-11-25 16:12             ` Mel Gorman
2010-11-26  1:05             ` Shaohua Li
2010-11-26  1:05               ` Shaohua Li
2010-11-26  1:25               ` Mel Gorman
2010-11-26  1:25                 ` Mel Gorman
2010-11-26  2:05                 ` Shaohua Li
2010-11-26  2:05                   ` Shaohua Li
2010-11-26 11:03             ` KOSAKI Motohiro
2010-11-26 11:03               ` KOSAKI Motohiro
2010-11-26 11:11               ` Mel Gorman
2010-11-26 11:11                 ` Mel Gorman
2010-11-30  6:31                 ` KOSAKI Motohiro
2010-11-30  6:31                   ` KOSAKI Motohiro
2010-11-30 10:41                   ` Mel Gorman
2010-11-30 10:41                     ` Mel Gorman
2010-11-30 11:19                     ` KOSAKI Motohiro
2010-11-30 11:19                       ` KOSAKI Motohiro
2010-11-30  8:22             ` Simon Kirby
2010-11-30  8:22               ` Simon Kirby
2010-11-29  9:31       ` KOSAKI Motohiro
2010-11-29  9:31         ` KOSAKI Motohiro
2010-11-23 10:04   ` Mel Gorman
2010-11-23 10:04     ` Mel Gorman
2010-11-24  6:43     ` Simon Kirby
2010-11-24  6:43       ` Simon Kirby
2010-11-24  9:27       ` Mel Gorman [this message]
2010-11-24  9:27         ` Mel Gorman
2010-11-24 19:17         ` Simon Kirby
2010-11-24 19:17           ` Simon Kirby
2010-11-25  1:18           ` KOSAKI Motohiro
2010-11-25  1:18             ` KOSAKI Motohiro
2010-11-26 15:48             ` Christoph Lameter
2010-11-26 15:48               ` Christoph Lameter
2010-11-30  0:25               ` KOSAKI Motohiro
2010-11-30  0:25                 ` KOSAKI Motohiro
2010-11-30 19:10                 ` Christoph Lameter
2010-11-30 19:10                   ` Christoph Lameter
2010-12-01 10:17                   ` KOSAKI Motohiro
2010-12-01 10:17                     ` KOSAKI Motohiro
2010-12-01 15:29                     ` Christoph Lameter
2010-12-01 15:29                       ` Christoph Lameter
2010-12-02  2:44                       ` KOSAKI Motohiro
2010-12-02  2:44                         ` KOSAKI Motohiro
2010-12-02 14:39                         ` Christoph Lameter
2010-12-02 14:39                           ` Christoph Lameter
2010-11-30  9:13               ` Simon Kirby
2010-11-30  9:13                 ` Simon Kirby
2010-11-30 19:13                 ` Christoph Lameter
2010-11-30 19:13                   ` Christoph Lameter

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=20101124092753.GS19571@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sim@hostway.ca \
    /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.