Hello, I am interested in how PulseAudio deal with zero copy. I have gone through paper "An Efficient Zero-Copy I/O Framework for UNIX" from 1995. I have review the PulseAudio code to look how it is implemented. In the paper, authors presented that the only implementation of memory pool possible for them is on kernel side. The PulseAudio way is to make it shared memory on user side. and I come with 2 questions Is it sufficient to open shared memory and mmap it into the application address space? How did you test the PulseAudio concerning zero copy of data? I would be very thankful if you could explain it to me, please. Pawel ---------------------------------------------------------------------- Drogowa Mapa Polski GPS w Twoim telefonie! Pobierz >> http://link.interia.pl/f1fc9
