Re: [PATCH 2/3] Use one zonelist that is filtered instead of multiple zonelists

On Wed, 8 Aug 2007, Mel Gorman wrote:

> The zone_id is the one I'm really interested in. It looks like the most
> promising optimisation for avoiding zone_idx in the hotpath.

Certainly the highest priority. However, if the nodeid could be coded in 
then we may be able to also avoid the GFP_THISNODE zonelists and improve 
the speed of matching a zonelist to a node mask.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 0/3] Use one zonelist per node instead of multiple zonelists v2
  - From: Mel Gorman <[email protected]>
- [PATCH 2/3] Use one zonelist that is filtered instead of multiple zonelists
  - From: Mel Gorman <[email protected]>
- Re: [PATCH 2/3] Use one zonelist that is filtered instead of multiple zonelists
  - From: Christoph Lameter <[email protected]>
- Re: [PATCH 2/3] Use one zonelist that is filtered instead of multiple zonelists
  - From: [email protected] (Mel Gorman)

Prev by Date: Re: [PATCH 0/3] Use one zonelist per node instead of multiple zonelists v2
Next by Date: Re: [PATCH] make atomic_t volatile on all architectures
Previous by thread: Re: [PATCH 2/3] Use one zonelist that is filtered instead of multiple zonelists
Next by thread: [PATCH 3/3] Apply MPOL_BIND policy to two highest zones when highest is ZONE_MOVABLE
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]