Re: [PATCH 2/2] blktrace: limit allowed total trace buffer size

2021-03-30 Thread Christoph Hellwig
On Tue, Mar 23, 2021 at 04:14:40PM +0800, Ming Lei wrote: > On some ARCHs, such as aarch64, page size may be 64K, meantime there may Which we call arm64.. > be lots of CPU cores. relay_open() needs to allocate pages on each CPU > blktrace, so easily too many pages are taken by blktrace. For

Re: [PATCH 2/2] blktrace: limit allowed total trace buffer size

2021-03-29 Thread Ming Lei
On Tue, Mar 30, 2021 at 10:57:04AM +0800, Su Yue wrote: > > On Tue 23 Mar 2021 at 16:14, Ming Lei wrote: > > > On some ARCHs, such as aarch64, page size may be 64K, meantime there may > > be lots of CPU cores. relay_open() needs to allocate pages on each CPU > > blktrace, so easily too many

Re: [PATCH 2/2] blktrace: limit allowed total trace buffer size

2021-03-29 Thread Su Yue
On Tue 23 Mar 2021 at 16:14, Ming Lei wrote: On some ARCHs, such as aarch64, page size may be 64K, meantime there may be lots of CPU cores. relay_open() needs to allocate pages on each CPU blktrace, so easily too many pages are taken by blktrace. For example, on one ARM64 server: 224 CPU

[PATCH 2/2] blktrace: limit allowed total trace buffer size

2021-03-23 Thread Ming Lei
On some ARCHs, such as aarch64, page size may be 64K, meantime there may be lots of CPU cores. relay_open() needs to allocate pages on each CPU blktrace, so easily too many pages are taken by blktrace. For example, on one ARM64 server: 224 CPU cores, 16G RAM, blktrace finally got allocated 7GB in