Re: [bug report] OOM caused by mlock() during exiting blktrace

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

 



Hi, Ming,

Ming Lei <tom.leiming@xxxxxxxxx> writes:

> Hello Guys,
>
> It is observed that nr_cpu * mlock(128M) is called when exiting
> 'blktrace -b 8192 -d $DEV'. And OOM is easily triggered when the
> machine has lots of CPU cores.

The only mlock in the code appears to happen at setup time.  How did you
determine this was occurring in the exit path?

> So can we figure out one way to not lock big buffer for avoiding
> OOM?

The obvious question is why are you using -b 8192?  Were you losing
events without that option?

-Jeff




[Index of Archives]     [Netdev]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux