Re: Avoiding external fragmentation with a placement policy Version 12

-		struct free_area *area;
 		struct page *buddy;
-
+		

...

 	}
+
 	spin_unlock_irqrestore(&zone->lock, flags);
-	return allocated;
+	return count - allocated;
 }

+

+

Other than the very minor whitespace changes above I have nothing bad to say about this patch. I think it is about time to pick in up in -mm for wider testing.

-
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: Avoiding external fragmentation with a placement policy Version 12
    • From: Mel Gorman <[email protected]>
  • Re: Avoiding external fragmentation with a placement policy Version 12
    • From: Nick Piggin <[email protected]>

• References:
  • Avoiding external fragmentation with a placement policy Version 12
    • From: [email protected] (Mel Gorman)

• Prev by Date: Re: Swap maximum size documented ?
• Next by Date: Re: RT patch acceptance
• Previous by thread: Avoiding external fragmentation with a placement policy Version 12
• Next by thread: Re: Avoiding external fragmentation with a placement policy Version 12
• 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]