Re: [PATCH v2] debugobjects: scale the static pool size

2018-11-20 Thread Thomas Gleixner
On Tue, 20 Nov 2018, Waiman Long wrote: > On 11/20/2018 03:14 PM, Qian Cai wrote: > > static struct debug_obj_descr *descr_test __read_mostly; > > The calculation for ODEBUG_POOL_SIZE is somewhat hard to read. Maybe you > can do something like > > #ifdef CONFIG_DEBUG_OBJECTS_WORK >

Re: [PATCH v2] debugobjects: scale the static pool size

2018-11-20 Thread Thomas Gleixner
On Tue, 20 Nov 2018, Waiman Long wrote: > On 11/20/2018 03:14 PM, Qian Cai wrote: > > static struct debug_obj_descr *descr_test __read_mostly; > > The calculation for ODEBUG_POOL_SIZE is somewhat hard to read. Maybe you > can do something like > > #ifdef CONFIG_DEBUG_OBJECTS_WORK >

Re: [PATCH v2] debugobjects: scale the static pool size

2018-11-20 Thread Waiman Long
On 11/20/2018 03:14 PM, Qian Cai wrote: > The current value of the early boot static pool size is not big enough > for systems with large number of CPUs with timer or/and workqueue > objects selected. As the results, systems have 60+ CPUs with both timer > and workqueue objects enabled could

Re: [PATCH v2] debugobjects: scale the static pool size

2018-11-20 Thread Waiman Long
On 11/20/2018 03:14 PM, Qian Cai wrote: > The current value of the early boot static pool size is not big enough > for systems with large number of CPUs with timer or/and workqueue > objects selected. As the results, systems have 60+ CPUs with both timer > and workqueue objects enabled could

[PATCH v2] debugobjects: scale the static pool size

2018-11-20 Thread Qian Cai
The current value of the early boot static pool size is not big enough for systems with large number of CPUs with timer or/and workqueue objects selected. As the results, systems have 60+ CPUs with both timer and workqueue objects enabled could trigger "ODEBUG: Out of memory. ODEBUG disabled".

[PATCH v2] debugobjects: scale the static pool size

2018-11-20 Thread Qian Cai
The current value of the early boot static pool size is not big enough for systems with large number of CPUs with timer or/and workqueue objects selected. As the results, systems have 60+ CPUs with both timer and workqueue objects enabled could trigger "ODEBUG: Out of memory. ODEBUG disabled".