[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1003090946180.28897@router.home>
Date: Tue, 9 Mar 2010 09:50:15 -0600 (CST)
From: Christoph Lameter <cl@...ux-foundation.org>
To: Mel Gorman <mel@....ul.ie>
cc: linux-mm@...ck.org, Nick Piggin <npiggin@...e.de>,
Christian Ehrhardt <ehrhardt@...ux.vnet.ibm.com>,
Chris Mason <chris.mason@...cle.com>,
Jens Axboe <jens.axboe@...cle.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] page-allocator: Under memory pressure, wait on
pressure to relieve instead of congestion
On Mon, 8 Mar 2010, Mel Gorman wrote:
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index 30fe668..72465c1 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -398,6 +398,9 @@ struct zone {
> unsigned long wait_table_hash_nr_entries;
> unsigned long wait_table_bits;
>
> + /* queue for processes waiting for pressure to relieve */
> + wait_queue_head_t *pressure_wq;
> +
> /*
The waitqueue is in a zone? But allocation occurs by scanning a
list of possible zones.
> +long zonepressure_wait(struct zone *zone, unsigned int order, long timeout)
So zone specific.
>
> - if (!page && gfp_mask & __GFP_NOFAIL)
> - congestion_wait(BLK_RW_ASYNC, HZ/50);
> + if (!page && gfp_mask & __GFP_NOFAIL) {
> + /* If still failing, wait for pressure on zone to relieve */
> + zonepressure_wait(preferred_zone, order, HZ/50);
The first zone is special therefore...
What happens if memory becomes available in another zone? Lets say we are
waiting on HIGHMEM and memory in ZONE_NORMAL becomes available?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists