On Thu, 19 Aug 1999 08:59:05 -0400 (EDT), Peter Desnoyers
<pjd@fred001.dynip.com> said:
> However, I think the mmap approach is a better fit for a sound card than
> for a networking device. Much like disk traffic and raw IO, there are a
> number of cases where you might want to transmit data that is already in
> application memory, and avoid copying it into an intermediate buffer.
> With map_user_kiobuf you can do this, while with mmap you can't.
> Does the map_user_kiobuf approach pass muster?
It should do. The big advantage you have is that by implementing IO via
kiobufs, your IO routines won't actually care in the slightest where the
memory is coming from. You can implement a mmap() interface later if
you want, creating a kiobuf and populating it from the mapped kernel
pages, and use exactly the same IO routines to work on that buffer as if
it had come from map_user_kiobuf().
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/