Re: [PATCH 2/3] mm/vmalloc: occupy newly allocated vmap block just after allocation

2015-03-13 21:12 GMT+09:00 Roman Pen : > Previous implementation allocates new vmap block and repeats search of a free > block from the very beginning, iterating over the CPU free list. > > Why it can be better?? > > 1. Allocation can happen on one CPU, but search can be done on another CPU. >I

[PATCH 2/3] mm/vmalloc: occupy newly allocated vmap block just after allocation

Previous implementation allocates new vmap block and repeats search of a free block from the very beginning, iterating over the CPU free list. Why it can be better?? 1. Allocation can happen on one CPU, but search can be done on another CPU. In worst case we preallocate amount of vmap blocks w