On Tue, May 21, 2013 at 01:08:21PM -0700, Lin Zhao wrote:
> Figured this out. It caused by huge buffer size, which is kind of like
> cache, but with disk meta data. The kernel won't release buffered memory
> unless the kernel tries to get more memory, and *buffered* memory
> accumulates over time.
Figured this out. It caused by huge buffer size, which is kind of like
cache, but with disk meta data. The kernel won't release buffered memory
unless the kernel tries to get more memory, and *buffered* memory
accumulates over time.
I ran a program that allocates a git chunk of memory and the buff
I've been running DRBD set up for 3 months, and recently noticed high
kernel memory usage on the secondary machines.
The secondary machine runs very light user applications, but total memory
usage reaches as much as 60G.
Is there a known issue with kernel message leak? Attaching top, slabtop and
