Re: [Discuss-gnuradio] gr::buffer::allocate_buffer: warning

[Anderson, Douglas J.]

Would it be possible to dive into this a bit deeper? I'm trying to get more familiar with the the scheduler and how the buffer is laid out.

So using "tried to allocate 41 items of size 1592. Due to alignment requirements 512 were allocated" as an example, the scheduler looked at the requirements of the various blocks (or does each block have a dedicated buffer?) and decided it needed buffers of at least 41x1592 bytes? But assuming no block explicitly called set_alignment(), the scheduler uses the default page size (4096 bytes) and just allocated a number of 1592-byte blocks such that (n * 1592) % 4096 == 0?

Am I on the right track with this?

-Doug

---

From: discuss-gnuradio-bounces+address@hidden [discuss-gnuradio-bounces+address@hidden on behalf of Ali Riaz address@hidden
Sent: Monday, April 20, 2015 12:16 PM
To: address@hidden
Subject: [Discuss-gnuradio] gr::buffer::allocate_buffer: warning

Hello everyone,

I'm getting the following warnings when running my application, does anyone know what this means?

gr::buffer::allocate_buffer: warning: tried to allocate
   41 items of size 1592. Due to alignment requirements
   512 were allocated.  If this isn't OK, consider padding
   your structure to a power-of-two bytes.
   On this platform, our allocation granularity is 4096 bytes.
gr::buffer::allocate_buffer: warning: tried to allocate
   82 items of size 796. Due to alignment requirements
   1024 were allocated.  If this isn't OK, consider padding
   your structure to a power-of-two bytes.
   On this platform, our allocation granularity is 4096 bytes.
gr::buffer::allocate_buffer: warning: tried to allocate
   82 items of size 796. Due to alignment requirements
   1024 were allocated.  If this isn't OK, consider padding
   your structure to a power-of-two bytes.
   On this platform, our allocation granularity is 4096 bytes.
gr::buffer::allocate_buffer: warning: tried to allocate
   82 items of size 796. Due to alignment requirements
   1024 were allocated.  If this isn't OK, consider padding
   your structure to a power-of-two bytes.
   On this platform, our allocation granularity is 4096 bytes

Best,

Ali