Re: kmem_alloc replacement in Tiger
Re: kmem_alloc replacement in Tiger
- Subject: Re: kmem_alloc replacement in Tiger
- From: Nikita Danilov <email@hidden>
- Date: Wed, 1 Feb 2006 08:28:44 +0300
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.
>
> = Mike
Nikita.
_______________________________________________
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