All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sami Farin <hvtaifwkbgefbaei@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: [BUG] How to crash 4.9.2 x86_64: vmscan: shrink_slab
Date: Tue, 10 Jan 2017 12:32:11 +0200	[thread overview]
Message-ID: <20170110103211.arb3sqv54hu4gdiy@m.mifar.in> (raw)
In-Reply-To: <20170110092241.GA28032@dhcp22.suse.cz>

On Tue, Jan 10, 2017 at 10:22:41 +0100, Michal Hocko wrote:
> On Mon 09-01-17 23:02:10, Sami Farin wrote:
> > # sysctl vm.vfs_cache_pressure=-100
> > 
> > kernel: vmscan: shrink_slab: super_cache_scan+0x0/0x1a0 negative objects to delete nr=-6640827866535449472
> > kernel: vmscan: shrink_slab: super_cache_scan+0x0/0x1a0 negative objects to delete nr=-6640827866535450112
...
> > 
> > 
> > Alternatively,
> > # sysctl vm.vfs_cache_pressure=10000000
> 
> Both values are insane and admins do not do insane things to their
> machines, do they?

Not on purpose, unless they are insane :)

Docs say:
"Increasing vfs_cache_pressure significantly beyond 100 may have
negative performance impact."
Nothing about crashing.

But anyways, the problem I originally had was:
with vm.vfs_cache_pressure=0 , dentry/inode caches are reclaimed
at a very alarming rate, and when I e.g. rescan quodlibet media
directory (only 30000 files), that takes a lot of time..  I only download
some files for a minute and dentry/inode caches are reclaimed,
or so it seems.  Still, SReclaimable keeps on increasing, when it gets to
about 6 GB , I increase vm.vfs_cache_pressure .... 

-- 
Do what you love because life is too short for anything else.
https://samifar.in/

WARNING: multiple messages have this Message-ID (diff)
From: Sami Farin <hvtaifwkbgefbaei@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: [BUG] How to crash 4.9.2 x86_64: vmscan: shrink_slab
Date: Tue, 10 Jan 2017 12:32:11 +0200	[thread overview]
Message-ID: <20170110103211.arb3sqv54hu4gdiy@m.mifar.in> (raw)
In-Reply-To: <20170110092241.GA28032@dhcp22.suse.cz>

On Tue, Jan 10, 2017 at 10:22:41 +0100, Michal Hocko wrote:
> On Mon 09-01-17 23:02:10, Sami Farin wrote:
> > # sysctl vm.vfs_cache_pressure=-100
> > 
> > kernel: vmscan: shrink_slab: super_cache_scan+0x0/0x1a0 negative objects to delete nr=-6640827866535449472
> > kernel: vmscan: shrink_slab: super_cache_scan+0x0/0x1a0 negative objects to delete nr=-6640827866535450112
...
> > 
> > 
> > Alternatively,
> > # sysctl vm.vfs_cache_pressure=10000000
> 
> Both values are insane and admins do not do insane things to their
> machines, do they?

Not on purpose, unless they are insane :)

Docs say:
"Increasing vfs_cache_pressure significantly beyond 100 may have
negative performance impact."
Nothing about crashing.

But anyways, the problem I originally had was:
with vm.vfs_cache_pressure=0 , dentry/inode caches are reclaimed
at a very alarming rate, and when I e.g. rescan quodlibet media
directory (only 30000 files), that takes a lot of time..  I only download
some files for a minute and dentry/inode caches are reclaimed,
or so it seems.  Still, SReclaimable keeps on increasing, when it gets to
about 6 GB , I increase vm.vfs_cache_pressure .... 

-- 
Do what you love because life is too short for anything else.
https://samifar.in/

--
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:[~2017-01-10 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 21:02 [BUG] How to crash 4.9.2 x86_64: vmscan: shrink_slab Sami Farin
2017-01-09 21:02 ` Sami Farin
2017-01-10  9:22 ` Michal Hocko
2017-01-10  9:22   ` Michal Hocko
2017-01-10 10:32   ` Sami Farin [this message]
2017-01-10 10:32     ` Sami Farin

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=20170110103211.arb3sqv54hu4gdiy@m.mifar.in \
    --to=hvtaifwkbgefbaei@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 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.