From: "Stephen C. Tweedie" <sct@redhat.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Mark Hemment <markhe@veritas.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] allocation looping + kswapd CPU cycles
Date: Thu, 10 May 2001 20:52:04 +0100 [thread overview]
Message-ID: <20010510205204.O16590@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0105100935040.31900-100000@alloc> <Pine.LNX.4.21.0105101341130.19732-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0105101341130.19732-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Thu, May 10, 2001 at 01:43:46PM -0300
Hi,
On Thu, May 10, 2001 at 01:43:46PM -0300, Marcelo Tosatti wrote:
> No. __GFP_FAIL can to try to reclaim pages from inactive clean.
>
> We just want to avoid __GFP_FAIL allocations from going to
> try_to_free_pages().
Why? __GFP_FAIL is only useful as an indication that the caller has
some magic mechanism for coping with failure. There's no other
information passed, so a brief call to try_to_free_pages is quite
appropriate.
--Stephen
WARNING: multiple messages have this Message-ID (diff)
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Mark Hemment <markhe@veritas.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] allocation looping + kswapd CPU cycles
Date: Thu, 10 May 2001 20:52:04 +0100 [thread overview]
Message-ID: <20010510205204.O16590@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0105101341130.19732-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Thu, May 10, 2001 at 01:43:46PM -0300
Hi,
On Thu, May 10, 2001 at 01:43:46PM -0300, Marcelo Tosatti wrote:
> No. __GFP_FAIL can to try to reclaim pages from inactive clean.
>
> We just want to avoid __GFP_FAIL allocations from going to
> try_to_free_pages().
Why? __GFP_FAIL is only useful as an indication that the caller has
some magic mechanism for coping with failure. There's no other
information passed, so a brief call to try_to_free_pages is quite
appropriate.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-10 19:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 11:56 [PATCH] allocation looping + kswapd CPU cycles Mark Hemment
2001-05-08 11:56 ` Mark Hemment
2001-05-08 14:54 ` Alex Bligh - linux-kernel
2001-05-08 14:54 ` Alex Bligh - linux-kernel
2001-05-08 17:23 ` Marcelo Tosatti
2001-05-08 17:23 ` Marcelo Tosatti
2001-05-08 19:21 ` Jens Axboe
2001-05-08 19:21 ` Jens Axboe
2001-05-08 20:25 ` David S. Miller
2001-05-08 20:25 ` David S. Miller
2001-05-09 9:46 ` Mark Hemment
2001-05-09 9:46 ` Mark Hemment
2001-05-09 16:36 ` Marcelo Tosatti
2001-05-09 16:36 ` Marcelo Tosatti
2001-05-10 8:41 ` Mark Hemment
2001-05-10 8:41 ` Mark Hemment
2001-05-10 16:43 ` Marcelo Tosatti
2001-05-10 16:43 ` Marcelo Tosatti
2001-05-10 19:52 ` Stephen C. Tweedie [this message]
2001-05-10 19:52 ` Stephen C. Tweedie
2001-05-10 18:22 ` Marcelo Tosatti
2001-05-10 18:22 ` Marcelo Tosatti
2001-05-10 20:19 ` Stephen C. Tweedie
2001-05-10 20:19 ` Stephen C. Tweedie
2001-05-10 18:49 ` Marcelo Tosatti
2001-05-10 18:49 ` Marcelo Tosatti
2001-05-10 20:52 ` Stephen C. Tweedie
2001-05-10 20:52 ` Stephen C. Tweedie
2001-05-12 14:56 ` Rik van Riel
2001-05-12 14:56 ` Rik van Riel
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=20010510205204.O16590@redhat.com \
--to=sct@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=markhe@veritas.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 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.