Re: [Discuss-gnuradio] why block's buffer was mapped to two address

2015-06-16 Thread Tom Rondeau
s-gnuradio"; > *Subject: * Re: [Discuss-gnuradio] why block's buffer was mapped to two > address > > Hi Tiankun Hu, > > I hope I'm answering the right question, but: > gr-buffer maps the same pages into memory multiple times, forming a > pseudo-ring buffer, so t

Re: [Discuss-gnuradio] why block's buffer was mapped to two address

2015-06-15 Thread Tiankun Hu
2015 10:03 PM To: "discuss-gnuradio"; Subject: Re: [Discuss-gnuradio] why block's buffer was mapped to two address Hi Tiankun Hu, I hope I'm answering the right question, but: gr-buffer maps the same pages into memory multiple times, forming a pseudo-ring buffer, so that

Re: [Discuss-gnuradio] why block's buffer was mapped to two address

2015-06-15 Thread Marcus Müller
Hi Tiankun Hu, I hope I'm answering the right question, but: gr-buffer maps the same pages into memory multiple times, forming a pseudo-ring buffer, so that no matter where in your buffer you start, you always get the full buffer length of "sequential data". This is very cool for algorithms that e

[Discuss-gnuradio] why block's buffer was mapped to two address

2015-06-15 Thread Tiankun Hu
Hi, I found block's buffer was mapped to two continues address, is there any benefit for this? When do update reader/writer pointer, I found they was rounded to the real buffer size, so I want to know which code will use this second half address? -- Thanks Tiankun _