Re: [PATCH 1/9] slab: add unlikely macro to help compiler

2014-02-14 Thread David Rientjes
On Fri, 14 Feb 2014, Joonsoo Kim wrote: > slab_should_failslab() is called on every allocation, so to optimize it > is reasonable. We normally don't allocate from kmem_cache. It is just > used when new kmem_cache is created, so it's very rare case. Therefore, > add unlikely macro to help compiler

Re: [PATCH 1/9] slab: add unlikely macro to help compiler

2014-02-14 Thread David Rientjes
On Fri, 14 Feb 2014, Joonsoo Kim wrote: slab_should_failslab() is called on every allocation, so to optimize it is reasonable. We normally don't allocate from kmem_cache. It is just used when new kmem_cache is created, so it's very rare case. Therefore, add unlikely macro to help compiler

[PATCH 1/9] slab: add unlikely macro to help compiler

2014-02-13 Thread Joonsoo Kim
slab_should_failslab() is called on every allocation, so to optimize it is reasonable. We normally don't allocate from kmem_cache. It is just used when new kmem_cache is created, so it's very rare case. Therefore, add unlikely macro to help compiler optimization. Signed-off-by: Joonsoo Kim diff

[PATCH 1/9] slab: add unlikely macro to help compiler

2014-02-13 Thread Joonsoo Kim
slab_should_failslab() is called on every allocation, so to optimize it is reasonable. We normally don't allocate from kmem_cache. It is just used when new kmem_cache is created, so it's very rare case. Therefore, add unlikely macro to help compiler optimization. Signed-off-by: Joonsoo Kim