Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE

On Fri, 26 Jan 2007, Mel Gorman wrote:

> Because Andrew has made it pretty clear he will not take those patches on the
> grounds of complexity - at least until it can be shown that they fix the e1000
> problem. Any improvement on the behavior of those patches such as address
> biasing to allow memory hot-remove of the higher addresses makes them even
> more complex.

What is the e1000 problem? Jumbo packet allocation via GFP_KERNEL?
-
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/

---

• Follow-Ups:
  • Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
    • From: Mel Gorman <[email protected]>

• References:
  • [PATCH 0/8] Create ZONE_MOVABLE to partition memory between movable and non-movable pages
    • From: Mel Gorman <[email protected]>
  • [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
    • From: Mel Gorman <[email protected]>
  • Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
    • From: Christoph Lameter <[email protected]>
  • Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
    • From: Mel Gorman <[email protected]>

• Prev by Date: Re: [PATCH 0/8] Create ZONE_MOVABLE to partition memory between movable and non-movable pages
• Next by Date: Re: O_DIRECT question
• Previous by thread: Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
• Next by thread: Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_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]