Re: [PATCH v2 5/5] mm/memcg: Optimize user context object stock access

On 4/12/21 7:10 PM, Shakeel Butt wrote: On Mon, Apr 12, 2021 at 3:55 PM Waiman Long wrote: Most kmem_cache_alloc() calls are from user context. With instrumentation enabled, the measured amount of kmem_cache_alloc() calls from non-task context was about 0.01% of the total. The irq disable/enab

Re: [PATCH v2 5/5] mm/memcg: Optimize user context object stock access

On Mon, Apr 12, 2021 at 4:10 PM Shakeel Butt wrote: > > On Mon, Apr 12, 2021 at 3:55 PM Waiman Long wrote: > > > > Most kmem_cache_alloc() calls are from user context. With instrumentation > > enabled, the measured amount of kmem_cache_alloc() calls from non-task > > context was about 0.01% of th

Re: [PATCH v2 5/5] mm/memcg: Optimize user context object stock access

On Mon, Apr 12, 2021 at 3:55 PM Waiman Long wrote: > > Most kmem_cache_alloc() calls are from user context. With instrumentation > enabled, the measured amount of kmem_cache_alloc() calls from non-task > context was about 0.01% of the total. > > The irq disable/enable sequence used in this case to

[PATCH v2 5/5] mm/memcg: Optimize user context object stock access

Most kmem_cache_alloc() calls are from user context. With instrumentation enabled, the measured amount of kmem_cache_alloc() calls from non-task context was about 0.01% of the total. The irq disable/enable sequence used in this case to access content from object stock is slow. To optimize for use