Re: [BUG] fatal hang untarring 90GB file, possibly writeback related.
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Tue, May 10, 2011 at 1:21 PM, Mel Gorman <mgorman@xxxxxxxxxx> wrote: > It goes on. A number of filesystem and network paths are being hit > with high-order allocs. i915 was a red herring, it's present but not > in massive numbers. The filesystem, network and mempool allocations > are likely to be kicking kswapd awake frequently and hurting overall > system performance as a result. > > I really would like to hear if the fix makes a big difference or > if we need to consider forcing SLUB high-order allocations bailing > at the first sign of trouble (e.g. by masking out __GFP_WAIT in > allocate_slab). Even with the fix applied, kswapd might be waking up > less but processes will still be getting stalled in direct compaction > and direct reclaim so it would still be jittery. Yes, sounds reasonable to me. Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Reiser Filesystem Development] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Linux FS] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]