Messages in this thread | | | Date | Fri, 03 Jun 2005 07:00:59 -0700 | From | "Martin J. Bligh" <> | Subject | Re: Avoiding external fragmentation with a placement policy Version 12 |
| |
> Does it need more documentation? If so, I'll write up a detailed blurb on > how it works and drop it into Documentation/ > >> Although I can't argue that a buddy allocator is no good without >> being able to satisfy higher order allocations. > > Unfortunately, it is a fundemental flaw of the buddy allocator that it > fragments badly. The thing is, other allocators that do not fragment are > also slower.
Do we care? 99.9% of allocations are fronted by the hot/cold page cache now anyway ... and yes, I realise that things popping in/out of that obviously aren't going into the "defrag" pool, but still, it should help. I suppose all we're slowing down is higher order allocs anyway, which is the uncommon case, but ... worth thinking about.
M.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |