Re: kmem_alloc replacement in Tiger
Re: kmem_alloc replacement in Tiger
- Subject: Re: kmem_alloc replacement in Tiger
- From: Mike Smith <email@hidden>
- Date: Tue, 31 Jan 2006 23:50:43 -0800
On Jan 31, 2006, at 9:28 PM, Nikita Danilov wrote:
Mike Smith writes:
On Jan 31, 2006, at 3:39 PM, Terry Lambert wrote:
Since Herb was talking about using the memory for a large array, I
recommended the API that I'd normally tell people to use for that
usage. If this array was actually a driver DMA target, well, then
one of the other options is probably a better bet.
Regardless of whether the memory is likely to be a DMA target or not,
allocating pageable kernel memory is probably the way to go.
The sole exception to this case is when the memory is likely to be
accessed on the paging path; typically anything in interrupt context
or on the low-level I/O path.
Or anything in a file-system. Or in a networking (when paging across
NFS)... basically almost anything.
Both of those are candidates, but I disagree with the "almost anything"
assertion.
And if you are on either of those paths, you should not be playing with
large allocations in the first place, as handling that much data
sounds suspiciously like being slow. 8)
= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden