On Wed, 8 Jun 2005, Martin J. Bligh wrote: > Right. I agree that large allocs should be reliable. Whether we care so > much about if they're performant or not, I don't know ... is an interesting > question. I think the answer is maybe not, within reason. The cost of > fishing in the allocator might well be irrelevant compared to the cost > of freeing the necessary memory area? Large consecutive page allocation is important for I/O. Lots of drivers are able to issue transfer requests spanning multiple pages which is only possible if the pages are in sequence. If memory is fragmented then this is no longer possible. - 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:
- References:
- Avoiding external fragmentation with a placement policy Version 12
- From: [email protected] (Mel Gorman)
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: Joel Schopp <[email protected]>
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: Nick Piggin <[email protected]>
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: "Martin J. Bligh" <[email protected]>
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: Nick Piggin <[email protected]>
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: "Martin J. Bligh" <[email protected]>
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: Nick Piggin <[email protected]>
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: Joel Schopp <[email protected]>
- Re: Avoiding external fragmentation with a placement policy Version 12
- From: Nick Piggin <[email protected]>
- 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: "Martin J. Bligh" <[email protected]>
- 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: "Martin J. Bligh" <[email protected]>
- Avoiding external fragmentation with a placement policy Version 12
- Prev by Date: Re: [Jfs-discussion] fsck.jfs segfaults on x86_64
- Next by Date: Re: PNP parallel&serial ports: module reload fails (2.6.11)?
- Previous by thread: Re: Avoiding external fragmentation with a placement policy Version 12
- Next by thread: Re: Avoiding external fragmentation with a placement policy Version 12
- Index(es):