Martin Bligh wrote:
What is really needed is to pass a physical address limit from the caller, together with a flag that says whether the memory needs to be mapped into the permanent kernel address space or not. The allocator then finds the set of zones that will fulfill this criteria. But I suspect this level of change will cause too many people to squeak loudly.
That's a good point and it will be something to keep in mind if we're going to rework the allocator API. Whether or not people will squeak, having callers say explicitly what type of memory they want will be much easier to audit/verify and more flexible in the long term (eg. allow a best effort allocation for odd sized masks, perhaps). Some sort of compatiblity (gfp flag -> address) mapping would be required to support legacy allocator APIs, but I don't think that would be a problem. -- SUSE Labs, Novell Inc.Send instant messages to your online friends http://au.messenger.yahoo.com -
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|