All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Robert Love <rml@tech9.net>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Andrea Arcangeli <andrea@suse.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: Remove PF_MEMDIE as it is redundant
Date: 09 Jan 2003 00:49:59 +0100	[thread overview]
Message-ID: <m2lm1v6w2g.fsf@demo.mitica> (raw)
In-Reply-To: <1042066824.694.3634.camel@phantasy>

>>>>> "robert" == Robert Love <rml@tech9.net> writes:

robert> On Wed, 2003-01-08 at 17:47, Juan Quintela wrote:
>> PF_MEMDIE don't have any use in current kernels.  Please
>> remove, we only set it in one place, and there we also set
>> PF_MEMALLOC.  And we only test it in other place, and we also
>> test for PF_MEMALLOC.  This patch has existed in aa for some
>> quite time.

robert> I independently thought this same thing, and did a patch for 2.5 which
robert> had the same effect.

robert> I was reminded by better-VM-hackers-than-I that PF_MEMALLOC can be
robert> cleared in various paths so the PF_MEMDIE is required to ensure that the
robert> check in page_alloc.c is always true for OOM'ed tasks.

That is a nice theory, and I think that this could be true in the
past, but in 2.4.2X, PF_MEMDIE only appears in the two places that I
show, and it is completely redundant, look at the patch, we are just 
|-ing both PF_MEMALLOC and PF_MEMDIE and later we are &-ing against
the or of the two.  Use find & grep yourself if you don't believe me.

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  reply	other threads:[~2003-01-08 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 22:47 [PATCH]: Remove PF_MEMDIE as it is redundant Juan Quintela
2003-01-08 23:00 ` Robert Love
2003-01-08 23:49   ` Juan Quintela [this message]
2003-01-08 23:46     ` Robert Love
2003-01-09  0:01       ` Juan Quintela

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=m2lm1v6w2g.fsf@demo.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rml@tech9.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.