On Wed, 26 Nov 2014, Andrew Morton wrote:
> You forgot something.
>
> ---
> a/fs/seq_file.c~fs-seq_file-fallback-to-vmalloc-instead-of-oom-kill-processes-fix
> +++ a/fs/seq_file.c
> @@ -36,6 +36,10 @@ static void *seq_buf_alloc(unsigned long
> {
> void *buf;
>
> + /*
> + * __GFP_NORETRY to avoid oom-killings with high-order allocations -
> + * it's better to fall back to vmalloc() than to kill things.
> + */
> buf = kmalloc(size, GFP_KERNEL | __GFP_NORETRY | __GFP_NOWARN);
> if (!buf && size > PAGE_SIZE)
> buf = vmalloc(size);
>
Thanks!
> Is __GFP_NORETRY our preferred way of preventing oom-killings? If so,
> it's a bit obscure - wouldn't it be better to create a
> __GFP_NO_OOM_KILL?
>
The slowpath tries to allocate, calls memory compaction if necessary,
tries to allocate, calls direct reclaim, tries to allocate, call the oom
killer and tries to allocate if we are going to loop, and then loop if
allowed. There's no need to try to allocate if we don't call the oom
killer since it won't succeed and there's no need to call the oom killer
to free memory if we aren't going to retry.
Even if __GFP_NO_OOM_KILL existed, it wouldn't be applicable to this
patch: the change here is that seqfile will now return -ENOMEM instead of
oom killing processes; the slab allocation will no longer loop forever
trying to allocate memory.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
