[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] sched is requesting more input data than we can p
From: |
Miklos Maroti |
Subject: |
Re: [Discuss-gnuradio] sched is requesting more input data than we can provide |
Date: |
Fri, 24 Jan 2014 07:28:49 +0100 |
Hi Marcus,
On Thu, Jan 23, 2014 at 10:12 PM, Marcus Müller <address@hidden> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Miklos,
>
> the problem here is xxx:
>
> On 23.01.2014 22:00, Miklos Maroti wrote:
>> sched: <xxx> is requesting more input data
>
> what's this xxx? It is requiring 16000 input items at once *at least*
> and that's nearly twice the max output size (see
> gnuradio-runtime/lib/block_executor.cc), and you're right, that has
> something to do with maximum buffer sizes.
> However, GNU Radio has algorithms to appropriately set up buffers to
> make the items flow. Unless you've configured the top_block
> explicitely to have max noutput items < 16000, that should work out
> unless there is some architectural quirk in your flowgraph that
> actually suggest that it /can't/ run.
I did not set anything explicitly, although I did not set in my xxx
block the set relative rate (maybe that is used by the scheduler to
set up the buffer sizes appropriately).
Basically I want to take 100 packets of size 160 and push them through
an S/P converter for an 128 point IFFT (think of OFDM where every
subcarrier would carry its own packets independently).
Miklos
>
> So, to help you out, we actually need a little more information.
> Most probably an architectural change to xxx or your flowgraph will
> solve your problem.
>
> Greetings,
> Marcus
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJS4YW+AAoJEAFxB7BbsDrLQlUH/0A0+QTTNSaun4ML91BKMbAy
> ga9wFwJQRLlR1CJewzGBHzAJhx7ruSSh3P3H4jEJb7Lg5zpHAUQ/qB7+AspobFZt
> HsYgmApPGv6ck0DyEe5SNiKKPr8HNCvf9t/hijBd8yNOWrPrjcDTR1GJQfy69yYJ
> oX11Y+1IOSFQI0mL6dKkcIJ6Q9tEV2J0qRQieLxF4CqO5dSLQ1W9HtfElVktrJ18
> a3BcxNhJLppKMZqlBwMommQCcoZ1+3J1KWlTxPP0dj58reEN9ub0vRKa98KtFXZI
> AbMWP1jaJrjDIgvRRPIU1txbKMIh4V77N1bg4fF0elHVD+5QAgh3HdiVQhyVPOU=
> =3zBJ
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
- [Discuss-gnuradio] sched is requesting more input data than we can provide, Miklos Maroti, 2014/01/23
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Marcus D. Leech, 2014/01/23
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Marcus Müller, 2014/01/23
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide,
Miklos Maroti <=
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Martin Braun, 2014/01/24
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Miklos Maroti, 2014/01/25
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Miklos Maroti, 2014/01/25
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Martin Braun, 2014/01/25
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Miklos Maroti, 2014/01/25
- Re: [Discuss-gnuradio] sched is requesting more input data than we can provide, Martin Braun, 2014/01/25