Hi everyone,

My question is around the following message:

"gr::buffer::allocate_buffer: warning: tried to allocate
   728 items of size 90. Due to alignment requirements
   2048 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."

The flowchart is as follows:

F1--->
            Framer   ---> F3
F2--->

[Framer has two inputs from F1 and F2, and outputs to F3]


there are four blocks:
F1:     {File source: char vector items in length N1, repeat=True}
F2:     {File source: char vector items in length N2, repeat=True}
Framer: {OOT: concatenates N1 and N2 and outputs char vector items in
length (N1+N2)}
F3:     {File sink: char vector items in length (N1+N2), in overwritten
mode}

The question is this: If I put N1=10 and N2=90 the message is:

"gr::buffer::allocate_buffer: warning: tried to allocate
   728 items of size 90. Due to alignment requirements
   2048 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."

If I change N1 and N2 to 11 and 89 (to keep the total fixed), respectively,
it is:

gr::buffer::allocate_buffer: warning: tried to allocate
   736 items of size 89. Due to alignment requirements
   4096 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.

If I change N1 and N2 to 12 and 88, respectively, there will be no message!

These two questions are killing me!!! :
    Question#1: I wonder form where these numbers (728, then 736, then
nothing...) come from??? I can't relate them to the 4096 buffer size!
    Question#2: If I change either F1 or F2 repeat modes to 'No', why is
the size of output file is always zero?


Regards,
Ali
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to