All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: rohit.seth@intel.com, akpm@osdl.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Clean up of __alloc_pages
Date: Sun, 30 Oct 2005 13:36:05 +1100	[thread overview]
Message-ID: <43643195.9040600@yahoo.com.au> (raw)
In-Reply-To: <20051029192611.79b9c5e7.pj@sgi.com>

Paul Jackson wrote:
>>> 2) The can_try_harder flag values were driving me nuts.
>>
>>Please instead use a second argument 'gfp_high', which will nicely
>>match zone_watermark_ok, and use that consistently when converting
>>__alloc_pages code to use get_page_from_freelist. Ie. keep current
>>behaviour.
> 
> 
> Well ... I still don't understand what you're suggesting, so I
> guess I will have to wait for an actual patch incorporating it.
> 

See how can_try_harder and gfp_high is used currently. They
are simple boolean values and are easily derived from parameters
passed into __alloc_pages.

> Are you also objecting to converting "can_try_harder" to an
> enum, and getting the values in order of desperation?  If so,
> I don't why you object.
> 

Because then to get current behaviour you would have to add
branches to get the correct enum value.

> And there is still the issue that I don't think cpuset constraints
> should be applied in the last attempt before oom_killing for
> GFP_ATOMIC requests.
> 

Sure.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: rohit.seth@intel.com, akpm@osdl.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Clean up of __alloc_pages
Date: Sun, 30 Oct 2005 13:36:05 +1100	[thread overview]
Message-ID: <43643195.9040600@yahoo.com.au> (raw)
In-Reply-To: <20051029192611.79b9c5e7.pj@sgi.com>

Paul Jackson wrote:
>>> 2) The can_try_harder flag values were driving me nuts.
>>
>>Please instead use a second argument 'gfp_high', which will nicely
>>match zone_watermark_ok, and use that consistently when converting
>>__alloc_pages code to use get_page_from_freelist. Ie. keep current
>>behaviour.
> 
> 
> Well ... I still don't understand what you're suggesting, so I
> guess I will have to wait for an actual patch incorporating it.
> 

See how can_try_harder and gfp_high is used currently. They
are simple boolean values and are easily derived from parameters
passed into __alloc_pages.

> Are you also objecting to converting "can_try_harder" to an
> enum, and getting the values in order of desperation?  If so,
> I don't why you object.
> 

Because then to get current behaviour you would have to add
branches to get the correct enum value.

> And there is still the issue that I don't think cpuset constraints
> should be applied in the last attempt before oom_killing for
> GFP_ATOMIC requests.
> 

Sure.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-10-30  2:34 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29  1:33 [PATCH]: Clean up of __alloc_pages Rohit, Seth
2005-10-29  1:33 ` Rohit, Seth
2005-10-29  2:33 ` Nick Piggin
2005-10-29  2:33   ` Nick Piggin
2005-10-31 20:55   ` Rohit Seth
2005-10-31 20:55     ` Rohit Seth
2005-11-01  1:14     ` Nick Piggin
2005-11-01  1:14       ` Nick Piggin
2005-11-04 18:15       ` Rohit Seth
2005-11-04 18:15         ` Rohit Seth
2005-11-05  0:00         ` Nick Piggin
2005-11-05  0:00           ` Nick Piggin
2005-10-30  0:16 ` Paul Jackson
2005-10-30  0:16   ` Paul Jackson
2005-10-31 19:09   ` Rohit Seth
2005-10-31 19:09     ` Rohit Seth
2005-11-05 17:09   ` Andi Kleen
2005-11-05 17:09     ` Andi Kleen
2005-11-06  4:18     ` Paul Jackson
2005-11-06  4:18       ` Paul Jackson
2005-11-06 17:35       ` Andi Kleen
2005-11-06 17:35         ` Andi Kleen
2005-11-06 20:49         ` Paul Jackson
2005-11-06 20:49           ` Paul Jackson
2005-11-07  2:57           ` Nick Piggin
2005-11-07  2:57             ` Nick Piggin
2005-11-07  3:42             ` Andi Kleen
2005-11-07  3:42               ` Andi Kleen
2005-11-07  4:37               ` Paul Jackson
2005-11-07  4:37                 ` Paul Jackson
2005-11-07  6:08                 ` Nick Piggin
2005-11-07  6:08                   ` Nick Piggin
2005-11-07  9:46                   ` Paul Jackson
2005-11-07  9:46                     ` Paul Jackson
2005-11-07 10:17                     ` Nick Piggin
2005-11-07 10:17                       ` Nick Piggin
2005-11-07 14:41                       ` Paul Jackson
2005-11-07 14:41                         ` Paul Jackson
2005-11-07  3:44             ` Paul Jackson
2005-11-07  3:44               ` Paul Jackson
2005-10-30  1:47 ` Paul Jackson
2005-10-30  1:47   ` Paul Jackson
2005-10-30  2:01   ` Nick Piggin
2005-10-30  2:01     ` Nick Piggin
2005-10-30  2:19     ` Paul Jackson
2005-10-30  2:19       ` Paul Jackson
2005-10-30  2:32       ` Nick Piggin
2005-10-30  2:32         ` Nick Piggin
2005-10-30  3:06         ` Paul Jackson
2005-10-30  3:06           ` Paul Jackson
2005-10-30  3:53           ` Nick Piggin
2005-10-30  3:53             ` Nick Piggin
2005-10-30  2:26     ` Paul Jackson
2005-10-30  2:26       ` Paul Jackson
2005-10-30  2:36       ` Nick Piggin [this message]
2005-10-30  2:36         ` Nick Piggin
2005-10-30  3:09         ` Paul Jackson
2005-10-30  3:09           ` Paul Jackson
2005-10-30  3:55           ` Nick Piggin
2005-10-30  3:55             ` Nick Piggin
2005-10-30  4:11             ` Paul Jackson
2005-10-30  4:11               ` Paul Jackson
2005-10-31 21:20   ` Rohit Seth
2005-10-31 21:20     ` Rohit Seth
2005-10-31 21:28     ` Paul Jackson
2005-10-31 21:28       ` Paul Jackson
  -- strict thread matches above, loose matches on Subject: below --
2005-11-05  1:57 Seth, Rohit
2005-11-05  1:57 ` Seth, Rohit
2005-10-01 19:00 Seth, Rohit
2005-10-01 19:00 ` Seth, Rohit
2005-10-02  3:09 ` Nick Piggin
2005-10-02  3:09   ` Nick Piggin
2005-10-03 16:50   ` Rohit Seth
2005-10-03 16:50     ` Rohit Seth
2005-10-03 15:34 ` Christoph Lameter
2005-10-03 15:34   ` Christoph Lameter
2005-10-03 16:55   ` Rohit Seth
2005-10-03 16:55     ` Rohit Seth
2005-10-03 16:57     ` Christoph Lameter
2005-10-03 16:57       ` Christoph Lameter
2005-10-03 17:48       ` Rohit Seth
2005-10-03 17:48         ` Rohit Seth
2005-10-04 13:27         ` Andi Kleen
2005-10-04 13:27           ` Andi Kleen
2005-10-04 16:26           ` Ray Bryant
2005-10-04 16:26             ` Ray Bryant
2005-10-04 16:10             ` Martin J. Bligh
2005-10-04 16:10               ` Martin J. Bligh
2005-10-04 17:02               ` Ray Bryant
2005-10-04 17:02                 ` Ray Bryant

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=43643195.9040600@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.com \
    --cc=rohit.seth@intel.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.