Hi Marcus:
Thank you so much.
1.How did the system know how many items I can consume in a work call?
2.Do you means that every times call the block,the block will throw the
ninput_items[0] items?
For example,the input steam 0 item is 1,2,3,4,5... and the
ninput_items[0]=2.
Hi Zswx,
On 07/09/2015 04:49 PM, zs wrote:
1.How did the system know how many items I can consume in a work call?
Because it's the one who supplies these -- hence, it knows how many exist!
2.Do you means that every times call the block,the block will throw
the ninput_items[0] items?
Hi Marcus:
Thank you so much.
1.How did the system know how many items I can consume in a work call?
2.Do you means that every times call the block,the block will throw the
ninput_items[0] items?
For example,the input steam 0 item is 1,2,3,4,5... and the
ninput_items[0]=2.
Hi,
Thank you in advance.I have a question about the ninput_items.I find the
meaning of it is vector of items available on all input buffers.
When I read the source code of crc32_bb_impl.cc,I see the code below,
int
65 crc32_bb_impl::work (int noutput_items,
66
Hi Zswx,
ninput_items[0] is really the number of items that you can consume in a
work call (on input stream 0). It's usually 1.
Best regards,
Marcus
On 07/09/2015 03:29 PM, zs wrote:
Hi,
Thank you in advance.I have a question about the ninput_items.I
find the meaning of it is vector of
