Re: mm/slab: What is cache_reap work for?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 27 Jun 2017, Tetsuo Handa wrote:

> I hit an unable to invoke the OOM killer lockup shown below. According to
> "cpus=2 node=0 flags=0x0 nice=0" part, it seems that cache_reap (in mm/slab.c)
> work stuck waiting for disk_events_workfn (in block/genhd.c) work to complete.

Cache reaping in SLAB is the expiration of objects since they are deemed
to be cache cold after while. Reaping is a tick driven worker thread that
calls other functions that are used during regular slab allocation and
freeing. Maybe someone added code that can cause deadlocks if invoked from
the tick?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]
  Powered by Linux