From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [GIT PULL] Shrinker fixes for XFS for 2.6.36-rc6
Date: Wed, 21 Jul 2010 09:32:38 +1000 [thread overview]
Message-ID: <20100720233238.GS32635@dastard> (raw)
In-Reply-To: <20100720004630.GH23223@dastard>
On Tue, Jul 20, 2010 at 10:46:30AM +1000, Dave Chinner wrote:
> Hi Linus,
>
> The following patches address shrinker lockdep and performance
> regressions introduced into XFS in 2.6.34 when a shrinker was
> added at the last moment to address OOM issues with lazy XFS inode
> reclaim.
>
> The first two patches are the saem as I originally posted to solve
> the problem for 2.6.34. They did not pass review in time for 2.6.34,
> and attempts to address said review comments resulted in a bigger,
> more contentious patchset that has much bigger issues than this
> patchset. Time has run out and I really don't want to have another
> kernel released with XFS causing lockdep to trigger the moment
> memory reclaim starts, so I'm asking if you will accept the original
> fixes I posted for the problem.
>
> The third patch addresses shrinker inode scanning performance
> problems raised in recently here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=16348
>
> Please consider these commits for 2.6.26-rc6.
Ijust rebased the series - the shrinker context patch did not pickup
the new shrinker in the TTM DRM code for radeon. New pull-request output
below.
Cheers,
Dave.
The following changes since commit d0c6f6258478e1dba532bf7c28e2cd6e1047d3a4:
Merge branch 'x86-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip (2010-07-19 13:19:32 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev shrinker
Dave Chinner (3):
mm: add context argument to shrinker callback
xfs: convert inode shrinker to per-filesystem contexts
xfs: track AGs with reclaimable inodes in per-ag radix tree
arch/x86/kvm/mmu.c | 2 +-
drivers/gpu/drm/i915/i915_gem.c | 2 +-
drivers/gpu/drm/ttm/ttm_page_alloc.c | 2 +-
fs/dcache.c | 2 +-
fs/gfs2/glock.c | 2 +-
fs/gfs2/quota.c | 2 +-
fs/gfs2/quota.h | 2 +-
fs/inode.c | 2 +-
fs/mbcache.c | 5 +-
fs/nfs/dir.c | 2 +-
fs/nfs/internal.h | 3 +-
fs/quota/dquot.c | 2 +-
fs/ubifs/shrinker.c | 2 +-
fs/ubifs/ubifs.h | 2 +-
fs/xfs/linux-2.6/xfs_buf.c | 5 +-
fs/xfs/linux-2.6/xfs_super.c | 2 -
fs/xfs/linux-2.6/xfs_sync.c | 130 ++++++++++++++++++++--------------
fs/xfs/linux-2.6/xfs_sync.h | 2 -
fs/xfs/linux-2.6/xfs_trace.h | 3 +
fs/xfs/quota/xfs_qm.c | 7 ++-
fs/xfs/xfs_mount.h | 2 +-
include/linux/mm.h | 2 +-
mm/vmscan.c | 8 ++-
net/sunrpc/auth.c | 2 +-
24 files changed, 113 insertions(+), 82 deletions(-)
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-20 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 0:46 [GIT PULL] Shrinker fixes for XFS for 2.6.36-rc6 Dave Chinner
2010-07-20 23:32 ` Dave Chinner [this message]
2010-07-20 23:35 ` Linus Torvalds
2010-07-21 5:21 ` Dave Chinner
2010-07-21 5:50 ` [GIT PULL] Shrinker conversion fixes Dave Chinner
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=20100720233238.GS32635@dastard \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.com \
/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