On Sun, Feb 8, 2015 at 5:44 AM, You Lizhao wrote:
> Hi Maroti and Braun,
>
> I ran into a similar problem. I tried to set the ninput_items_required[i]
> = 1, then the same output
>
> sched: is requesting more input data
> than we can provide.
> ninput_items_required = 1
> max_possi
Hi Maroti and Braun,
I ran into a similar problem. I tried to set the ninput_items_required[i] =
1, then the same output
sched: is requesting more input data
than we can provide.
ninput_items_required = 1
max_possible_items_available = 8191
If this is a filter, consider reducing
On 01/25/2014 02:59 PM, Miklos Maroti wrote:
> Hi Martin,
>
> But the buffers are already allocated, and I assume that they are not
> resized dynamically. So even if you change the relative rate at
> runtime, you will get into the "sched: is requesting more input
> data than we can provide" error
Hi Martin,
But the buffers are already allocated, and I assume that they are not
resized dynamically. So even if you change the relative rate at
runtime, you will get into the "sched: is requesting more input
data than we can provide" error. So I do not understand how the
scheduler is going to us
On 01/25/2014 02:23 PM, Miklos Maroti wrote:
> One more question:
>
> Can I change the relative rate (with set_relative_rate) while the
> flowgraph is running? What effect does that have?
Yes, you can. As you said, the relative rate is a pointer for the
scheduler to figure out how much stuff you
One more question:
Can I change the relative rate (with set_relative_rate) while the
flowgraph is running? What effect does that have?
Miklos
On Sat, Jan 25, 2014 at 12:07 PM, Miklos Maroti
wrote:
> Hi Martin,
>
> Ok, I think I have fixed the problem. I did not set the relative rate
> properly
Hi Martin,
Ok, I think I have fixed the problem. I did not set the relative rate
properly in the constructor. It seems, that the scheduler uses the
relative rates to allocate buffers before the graph is executed, and
if some block is requesting more data at runtime, then we get into
problems. It i
On 01/24/2014 07:28 AM, Miklos Maroti wrote:
>> 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
Hi Marcus,
On Thu, Jan 23, 2014 at 10:12 PM, Marcus Müller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Miklos,
>
> the problem here is xxx:
>
> On 23.01.2014 22:00, Miklos Maroti wrote:
>> sched: is requesting more input data
>
> what's this xxx? It is requiring 16000 input i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Miklos,
the problem here is xxx:
On 23.01.2014 22:00, Miklos Maroti wrote:
> sched: 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-run
On 01/23/2014 04:00 PM, Miklos Maroti wrote:
Hi!
I am getting this error:
sched: is requesting more input data
than we can provide.
ninput_items_required = 16000
max_possible_items_available = 8191
and I have no idea how to fix it. Is it possible to request more
buffer space? Setting
Hi!
I am getting this error:
sched: is requesting more input data
than we can provide.
ninput_items_required = 16000
max_possible_items_available = 8191
and I have no idea how to fix it. Is it possible to request more
buffer space? Setting the minimum output buffer size seems to have no
e
12 matches
Mail list logo
