discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] how to remove/suppress gr_buffer::allocate_buffer


From: Johannes Schmitz
Subject: Re: [Discuss-gnuradio] how to remove/suppress gr_buffer::allocate_buffer: warning:
Date: Fri, 17 Jun 2011 17:08:31 +0200

Hello Martin,
I will check my code to find out why it is so big.

Is there an easy way to somehow suppress this warning in case I am
willing to ignore it?

Johannes

2011/6/17 Martin Braun <address@hidden>:
> On Fri, Jun 17, 2011 at 03:42:07PM +0200, Johannes Schmitz wrote:
>> I am getting the following warning when running my script:
>>
>> gr_buffer::allocate_buffer: warning: tried to allocate
>>    4 items of size 88192. Due to alignment requirements
>>    32 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.
>>
>> Can somebody tell me how to solve this problem or suppress this warning?
>>
>> I found it has to do something with fft-size that is not power of 2..
>
> Buffers between blocks are always an integer multiple of the
> item-size (in your case 88192) and 4096. The LCM of 88192 and 4096
> is pretty large, and tadaa, you get a warning.
>
> It's just a warning. If everything works fine... just ignore it. But
> it's a waste of memory. If you want to optimize this, change your
> itemsize. You will normally have to adapt the way the data is handled,
> e.g., you could pad the input to 90112=22*4096 and then discard
> 90112-88192=1920 Bytes of every input vector.
>
> Personally, I usually just ignore it, since it rarely turns up in less
> unusual applications.
>
> MB
>
> --
> Karlsruhe Institute of Technology (KIT)
> Communications Engineering Lab (CEL)
>
> Dipl.-Ing. Martin Braun
> Research Associate
>
> Kaiserstraße 12
> Building 05.01
> 76131 Karlsruhe
>
> Phone: +49 721 608-43790
> Fax: +49 721 608-46071
> www.cel.kit.edu
>
> KIT -- University of the State of Baden-Württemberg and
> National Laboratory of the Helmholtz Association
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]