| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | [PATCH 0/2] xfs: write back inodes during reclaim |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 7 Apr 2011 16:19:54 +1000 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx |
This series fixes an OOM problem where VFS-only dirty inodes accumulate on an XFS filesystem due to atime updates causing OOM to occur. The first patch fixes a deadlock triggering bdi-flusher writeback from memory reclaim when a new bdi-flusher thread needs to be forked and no memory is available. the second adds a bdi-flusher kick from XFS's inode cache shrinker so that when memory is low the VFS starts writing back dirty inodes so they can be reclaimed as they get cleaned rather than remaining dirty and pinning the inode cache in memory. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 1/2] bdi: mark the bdi flusher busy when being forked, Dave Chinner |
|---|---|
| Next by Date: | [PATCH] xfs: fix xfs_itruncate_start tracing, Dave Chinner |
| Previous by Thread: | [PATCH 0/9] xfs; candidate fixes for 2.6.39 V2, Dave Chinner |
| Next by Thread: | [PATCH 2/2] xfs: kick inode writeback when low on memory, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |