public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Paul Jackson <pj@sgi.com>,
	Christoph Lameter <clameter@engr.sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch -mm] cpusets: allow TIF_MEMDIE threads to allocate anywhere
Date: Mon, 23 Apr 2007 22:03:13 +0200	[thread overview]
Message-ID: <200704232203.13659.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0704231235280.18240@chino.kir.corp.google.com>


> +        /*
> +         * Allow tasks that have access to memory reserves because they have
> +         * been OOM killed to get memory anywhere.
> +         */
> +        if (unlikely(test_tsk_thread_flag(current, TIF_MEMDIE)))

This should be test_thread_flag()

-Andi

  reply	other threads:[~2007-04-23 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 19:41 [patch -mm] cpusets: allow TIF_MEMDIE threads to allocate anywhere David Rientjes
2007-04-23 20:03 ` Andi Kleen [this message]
2007-04-23 20:55   ` [patch -mm v2] " David Rientjes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200704232203.13659.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=rientjes@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox