g+
g+ Communities
Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
<== Date ==> <== Thread ==>

Subject: Re: double buffered waveformRecord
From: Michael Davidsaver <mdavidsaver@bnl.gov>
To: core-talk@aps.anl.gov
Date: Fri, 11 Jan 2013 09:32:10 -0500
Hi Ralph,

I agree that this would be the ideal feature and, by allowing
DBADDR::pfield to be safely overwritten, I think it can be done.

Michael


On 01/11/13 04:14, Ralph Lange wrote:
> One thought...
> 
> I can easily imagine situations, e.g with cameras or acquisition cards,
> where a low-level driver (maybe shipped as binary) provides a new
> pointer to an array with every callback. I would really like an array
> record to be able to use this driver-allocated buffer, without copying,
> hopefully up to the network layer.
> Restricting the out-of-bounds-offset hack to one allocated chunk of
> memory would not serve this case, would it?
> 
> ~Ralph
> 

Replies:
Re: double buffered waveformRecord Michael Davidsaver
References:
double buffered waveformRecord Michael Davidsaver
Re: double buffered waveformRecord Andrew Johnson
Re: double buffered waveformRecord Michael Davidsaver
Re: double buffered waveformRecord Andrew Johnson
Re: double buffered waveformRecord Ralph Lange

Navigate by Date:
Prev: Re: double buffered waveformRecord Ralph Lange
Next: Re: double buffered waveformRecord Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
Navigate by Thread:
Prev: Re: double buffered waveformRecord Ralph Lange
Next: Re: double buffered waveformRecord Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICSv4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·