Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1558288

Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying.

From Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying.
Date 2017-01-13 13:00 +0100
Message-ID <sZ8Gu-ol-13@gated-at.bofh.it> (permalink)
References (5 earlier) <sSBNf-4du-21@gated-at.bofh.it> <sSBNf-4du-9@gated-at.bofh.it> <sYOop-4Za-19@gated-at.bofh.it> <sYZMR-3st-9@gated-at.bofh.it> <sZ7U6-7f-21@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On (01/13/17 12:03), Petr Mladek wrote:
[..]
> > why can't we?
> 
> Because it would newer call cond_resched() in non-preemptive kernel
> with CONFIG_PREEMPT_COUNT disabled. IMHO, we want to call it,
> for example, when we scroll the entire screen from tty_operations.
> 
> Or do I miss anything?

so... basically. it has never called cond_resched() there. right?
why is this suddenly a problem now?

	-ss

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying. Petr Mladek <pmladek@suse.com> - 2017-01-12 15:20 +0100
  Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying. Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-01-13 03:30 +0100
    Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying. Petr Mladek <pmladek@suse.com> - 2017-01-13 12:10 +0100
      Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying. Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-01-13 13:00 +0100
        Re: [PATCH] mm/page_alloc: Wait for oom_lock before retrying. Petr Mladek <pmladek@suse.com> - 2017-01-13 13:20 +0100

csiph-web