Hi Marcus, Yes, I understand the page size limitation. However, if your vector is 1234 bytes, then you can happily allocate 4096 size buffer, but the the block you always give out the multiple of 1234 byes (i.e. 1, 2 or 3 vectors). The address space wrapping would work fine, so the start of the vectors would not be always at the same place. I think it could be done, the question is whether it is worth to do it.
Miklos On Wed, Aug 21, 2013 at 9:46 PM, Marcus D. Leech <mle...@ripnet.com> wrote: >> Yes, this is what I am doing, but it is not very nice, and you cannot >> easily mix in blocks that want to work at the stream level. What >> really bugs me that I think the scheduler could figure all out, and >> treat my vectors as a stream, allocate nice buffers (who cares if the >> vector fits in the buffer in an integer multiple times). Am I wrong >> with this? I think this would be a nice further development... Miklos >> >> > The aligned-to-page-size buffer management is due to the way that mmap() is > used to mutliply-map these buffers into the address space. > That only "works" if the sizes are multiples of the native page size. > > > -- > Marcus Leech > Principal Investigator > Shirleys Bay Radio Astronomy Consortium > http://www.sbrac.org > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
