On Wednesday, June 5, 2002, at 09:08 PM, Scott Taggart wrote: I have seen various posts, responses, etc. on this subject, but quite frankly, I got lost. I have the need to take a slug of kernel memory in my driver and make it available to my user app so that my app can access it directly Does it have to go this way? Can you take a slug of user memory and make it available in the driver? That's the easiest and most straightforward (create a IOMemoryDescriptor from the user task and address range, and map it into the kernel). (I'll take care of arbitration and protection with my driver). ...he says unwittingly before really knowing what he is signing up for.... ;-) Oh, you mean inside that hunk of memory. That's the easy part. It's the managing of access to the memory as a whole (from outside pressures like copy-on-write, etc...) that's the tricky part. And it's also why you need to stick with the standard approaches. --Jim _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.