On Thu 02-03-17 08:41:58, Brian Foster wrote: > On Thu, Mar 02, 2017 at 02:27:55PM +0100, Michal Hocko wrote: [...] > > I see your argument about being in sync with other kmem helpers but > > those are bit different because regular page/slab allocators allow never > > fail semantic (even though this is mostly ignored by those helpers which > > implement their own retries but that is a different topic). > > > > ... but what I'm trying to understand here is whether this failure > scenario is specific to vmalloc() or whether the other kmem_*() > functions are susceptible to the same problem. For example, suppose we > replaced this kmem_zalloc_greedy() call with a kmem_zalloc(PAGE_SIZE, > KM_SLEEP) call. Could we hit the same problem if the process is killed? Well, kmem_zalloc uses kmalloc which can also fail when we are out of memory but in that case we can expect the OOM killer releasing some memory which would allow us to make a forward progress on the next retry. So essentially retrying around kmalloc is much more safe in this regard. Failing vmalloc might be permanent because there is no vmalloc space to allocate from or much more likely due to already mentioned patch. So vmalloc is different, really. -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
