mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: noahm@csail.mit.edu, linux-kernel@vger.kernel.org
Subject: Re: OOM problems with 2.6.11-rc4
Date: Wed, 16 Mar 2005 04:04:35 -0800	[thread overview]
Message-ID: <20050316040435.39533675.akpm@osdl.org> (raw)
In-Reply-To: <20050316003134.GY7699@opteron.random>

Andrea Arcangeli <andrea@suse.de> wrote:
>
> the VM is setting all_unreclaimable on the
> normal zone without any care about the progress we're making at freeing
> the slab.

Urgh, I didn't notice that all_unreclaimable is set.

> Beware this absolutely untested and it may not be enough.  Perhaps there
> are more bugs in the same area (the shrink_slab itself seems overkill
> complicated for no good reason and different methods returns random
> stuff, dcache returns a percentage of the free entries, dquot instead
> returns the allocated inuse entries too which makes the whole API
> looking unreliable).

No, the two functions are equivalent for the default value of
vfs_cache_pressure (100) - it's not a percentage.  It's just that we forgot
about the quota cache when adding the tunable.  And mbcache, come to that.

> Signed-off-by: Andrea Arcangeli <andrea@suse.de>
> 
> --- x/mm/vmscan.c.~1~	2005-03-14 05:02:17.000000000 +0100
> +++ x/mm/vmscan.c	2005-03-16 01:28:16.000000000 +0100
> @@ -1074,8 +1074,9 @@ scan:
>  			total_scanned += sc.nr_scanned;
>  			if (zone->all_unreclaimable)
>  				continue;
> -			if (zone->pages_scanned >= (zone->nr_active +
> -							zone->nr_inactive) * 4)

A change we made a while back effectively doubles the rate at which
pages_scanned gets incremented here (we now account for the active list as
well as the inactive list).  So this should be *8 to make it more
equivalent to the old code.  Not that this is likely to make much
difference.


> +			if (!reclaim_state->reclaimed_slab &&
> +			    zone->pages_scanned >= (zone->nr_active +
> +						    zone->nr_inactive) * 4)
>  				zone->all_unreclaimable = 1;

That might not change anything because we clear ->all_unreclaimable in
free_page_bulk().  Although that is behind the per-cpu-pages, so there will
be some lag.  And this change will cause us to not bale out of reclaim..

Still, I think it would make more sense to return a success indication from
shrink_slab() if we actually freed any slab objects.  That will prevent us
from incorrectly going all_unreclaimable if all we happen to be doing is
increasing slab internal fragmentation.

We could do that kludgily by re-polling the shrinker but it would be better
to return a second value from all the shrinkers.

> --- x/fs/dquot.c.~1~	2005-03-08 01:02:13.000000000 +0100
> +++ x/fs/dquot.c	2005-03-16 01:18:19.000000000 +0100
> @@ -510,7 +510,7 @@ static int shrink_dqcache_memory(int nr,
>  	spin_lock(&dq_list_lock);
>  	if (nr)
>  		prune_dqcache(nr);
> -	ret = dqstats.allocated_dquots;
> +	ret = (dqstats.free_dquots / 100) * sysctl_vfs_cache_pressure;
>  	spin_unlock(&dq_list_lock);
>  	return ret;
>  }

yup.

  parent reply	other threads:[~2005-03-16 12:05 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 20:44 Noah Meyerhans
2005-03-15 21:56 ` Sean
2005-03-15 22:12   ` Lee Revell
2005-03-15 23:46 ` Andrew Morton
2005-03-18 16:12   ` Noah Meyerhans
2005-04-13 13:47     ` Andrea Arcangeli
2005-04-14 16:56       ` Noah Meyerhans
2005-03-16  0:31 ` Andrea Arcangeli
2005-03-16 11:12   ` Andrea Arcangeli
2005-03-16 12:04   ` Andrew Morton [this message]
2005-03-16 12:15     ` Andrew Morton
2005-03-16 18:37     ` Andrea Arcangeli
2005-03-16 22:21       ` Andrew Morton
2005-03-23 19:53       ` OOM problems on 2.6.12-rc1 with many fsx tests Mingming Cao
2005-03-23 22:49         ` Andrew Morton
2005-03-23 23:13           ` Martin J. Bligh
2005-03-23 23:20             ` Andrew Morton
2005-03-23 23:26               ` Andries Brouwer
2005-03-23 23:30                 ` Martin J. Bligh
2005-03-23 23:42                   ` Andrew Morton
2005-03-23 23:49                     ` [Ext2-devel] " Badari Pulavarty
2005-03-24  1:49                     ` Andrea Arcangeli
2005-03-24  2:00                       ` Andrew Morton
2005-03-25 21:56         ` Andrew Morton
2005-03-25 22:11           ` [Ext2-devel] " Badari Pulavarty
2005-03-27  0:23             ` Mingming Cao
2005-03-27 19:22               ` Mingming Cao
2005-03-27 20:06                 ` Badari Pulavarty
2005-03-27 20:17                   ` Badari Pulavarty
2005-03-26  0:17         ` Dave Jones
2005-03-26  0:20           ` [Ext2-devel] " Badari Pulavarty
2005-04-04  1:35         ` Andrew Morton
2005-04-04 16:50           ` Mingming Cao
2005-04-04 20:04             ` Andrew Morton
2005-04-04 20:24               ` Martin J. Bligh
2005-04-04 20:33                 ` Andrew Morton
2005-04-05 17:04               ` [Ext2-devel] " Mingming Cao
2005-04-06  1:23                 ` Andrew Morton
2005-04-12 12:50                   ` Stephen C. Tweedie
2005-04-05 16:44           ` Stephen C. Tweedie
2005-03-16 12:23   ` OOM problems with 2.6.11-rc4 Andrew Morton
2005-03-16 12:30   ` 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=20050316040435.39533675.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noahm@csail.mit.edu \
    /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

all inboxes | Powered by JetHome®