On Thu, Mar 29, 2007 at 06:27:24PM -0700, Dan Halperin wrote:
> Eric Blossom wrote:
> > On Thu, Mar 29, 2007 at 05:16:45PM -0700, Dan Halperin wrote:
> >
> >> Since this block initially starts with 0 inputs and is not filled with
> >> other data following the run of the program, the last <10 sam
Eric Blossom wrote:
> On Thu, Mar 29, 2007 at 05:16:45PM -0700, Dan Halperin wrote:
>
>> Greg Troxel wrote:
>>
>>> I wonder if there is data somewhere in the flowgraph that's less than
>>> the amount needed for the next block to run. Perhaps there should
>>> be some sort of drain operatio
On Thu, Mar 29, 2007 at 05:16:45PM -0700, Dan Halperin wrote:
> Greg Troxel wrote:
> > I wonder if there is data somewhere in the flowgraph that's less than
> > the amount needed for the next block to run. Perhaps there should
> > be some sort of drain operation, or query for this (that adds over
Greg Troxel wrote:
> I wonder if there is data somewhere in the flowgraph that's less than
> the amount needed for the next block to run. Perhaps there should
> be some sort of drain operation, or query for this (that adds over
> components), so one can find out what's going on.
>
This appear
Dan Halperin wrote:
> This is the final state of the flow graph:
>
> regular 2:1
> max_items_avail = 9
> noutput_items = 8191
> BLKD_IN
> were_done
I realized that the other two flow graph elements with max_items_avail >
0 have the same max_items_avail at initialization; this makes sense
(Eric, sorry I keep failing to reply all)
Eric Blossom wrote:
> On Thu, Mar 29, 2007 at 08:01:38AM -0700, Eric Blossom wrote:
>
>> On Thu, Mar 29, 2007 at 08:04:22AM -0400, Greg Troxel wrote:
>>
>>> I wonder if there is data somewhere in the flowgraph that's less than
>>> the amount needed
On Thu, Mar 29, 2007 at 08:01:38AM -0700, Eric Blossom wrote:
> On Thu, Mar 29, 2007 at 08:04:22AM -0400, Greg Troxel wrote:
> >
> > I wonder if there is data somewhere in the flowgraph that's less than
> > the amount needed for the next block to run. Perhaps there should
> > be some sort of dra
On Thu, Mar 29, 2007 at 08:04:22AM -0400, Greg Troxel wrote:
> Eric Blossom <[EMAIL PROTECTED]> writes:
>
> > On Wed, Mar 28, 2007 at 09:39:14PM -0700, Dan Halperin wrote:
> >> Same loopback code I emailed about earlier; this time I attached the
> >> complete file (modulo some cleanup).
> >>
> >
Eric Blossom <[EMAIL PROTECTED]> writes:
> On Wed, Mar 28, 2007 at 09:39:14PM -0700, Dan Halperin wrote:
>> Same loopback code I emailed about earlier; this time I attached the
>> complete file (modulo some cleanup).
>>
>> Here's my input file (in stupid x86 short ordering..):
>>
>>$ hexdum
Eric Blossom wrote:
On Wed, Mar 28, 2007 at 09:39:14PM -0700, Dan Halperin wrote:
Same loopback code I emailed about earlier; this time I attached the
complete file (modulo some cleanup).
Here's my input file (in stupid x86 short ordering..):
$ hexdump input.txt
000 bbaa ddcc ffe
On Wed, Mar 28, 2007 at 09:39:14PM -0700, Dan Halperin wrote:
> Same loopback code I emailed about earlier; this time I attached the
> complete file (modulo some cleanup).
>
> Here's my input file (in stupid x86 short ordering..):
>
>$ hexdump input.txt
>000 bbaa ddcc ffee 1100 3322
Same loopback code I emailed about earlier; this time I attached the
complete file (modulo some cleanup).
Here's my input file (in stupid x86 short ordering..):
$ hexdump input.txt
000 bbaa ddcc ffee 1100 3322 5544 7766 9988
and then after going through loopback.py and being packed b
12 matches
Mail list logo
