On 05/29/2011 10:22 AM, Alexander Chemeris wrote:
On Sun, May 29, 2011 at 03:05, Marcus D. Leech mle...@ripnet.com wrote:
On 05/28/2011 04:28 PM, Alexander Chemeris wrote:
So, while this method is simple and good for non-realtime
applications, it doesn't fit our needs. It may be usable for
On Sun, May 29, 2011 at 23:57, Colby Boyer colby.bo...@gmail.com wrote:
On Sun, May 29, 2011 at 1:22 AM, Alexander Chemeris
alexander.cheme...@gmail.com wrote:
On Sun, May 29, 2011 at 03:05, Marcus D. Leech mle...@ripnet.com wrote:
On 05/28/2011 04:28 PM, Alexander Chemeris wrote:
So, while
On Mon, May 30, 2011 at 12:54, Andre Puschmann
andre.puschm...@tu-ilmenau.de wrote:
On 05/29/2011 10:22 AM, Alexander Chemeris wrote:
On Sun, May 29, 2011 at 03:05, Marcus D. Leech mle...@ripnet.com wrote:
On 05/28/2011 04:28 PM, Alexander Chemeris wrote:
So, while this method is simple and
On 30/05/2011 9:51 AM, Alexander Chemeris wrote:
Linux' pipe implementation is known to be quite slow. I would suggest to
use UNIX sockets instead. They should perform much better in terms of
latency and performance.
Good idea.
I'm dubious of such a claim--the core mechanisms between
On 05/30/2011 03:55 PM, Marcus D. Leech wrote:
On 30/05/2011 9:51 AM, Alexander Chemeris wrote:
Linux' pipe implementation is known to be quite slow. I would suggest to
use UNIX sockets instead. They should perform much better in terms of
latency and performance.
Good idea.
I'm dubious of
On Mon, May 30, 2011 at 18:30, Andre Puschmann
andre.puschm...@tu-ilmenau.de wrote:
On 05/30/2011 03:55 PM, Marcus D. Leech wrote:
On 30/05/2011 9:51 AM, Alexander Chemeris wrote:
Linux' pipe implementation is known to be quite slow. I would suggest to
use UNIX sockets instead. They should
On Sun, May 29, 2011 at 03:05, Marcus D. Leech mle...@ripnet.com wrote:
On 05/28/2011 04:28 PM, Alexander Chemeris wrote:
So, while this method is simple and good for non-realtime
applications, it doesn't fit our needs. It may be usable for PHY-MAC
interaction, but even here I'm not sure it
On Sun, May 29, 2011 at 1:22 AM, Alexander Chemeris
alexander.cheme...@gmail.com wrote:
On Sun, May 29, 2011 at 03:05, Marcus D. Leech mle...@ripnet.com wrote:
On 05/28/2011 04:28 PM, Alexander Chemeris wrote:
So, while this method is simple and good for non-realtime
applications, it doesn't
I evaluated latency of a FIFO (actually an ordinary pipe, but the kernel
mechanisms are identical), and measured 30usecs average on my
1.2GHz AMD Phenom system with plenty 'o memory.
I sent timestamps across the FIFO (struct timeval), and the reader
grabbed the local time of day, and
On Sat, May 28, 2011 at 22:06, Marcus D. Leech mle...@ripnet.com wrote:
I evaluated latency of a FIFO (actually an ordinary pipe, but the kernel
mechanisms are identical), and measured 30usecs average on my
1.2GHz AMD Phenom system with plenty 'o memory.
I sent timestamps across the FIFO
On Sat, May 28, 2011 at 22:06, Marcus D. Leechmle...@ripnet.com wrote:
I evaluated latency of a FIFO (actually an ordinary pipe, but the kernel
mechanisms are identical), and measured 30usecs average on my
1.2GHz AMD Phenom system with plenty 'o memory.
I sent timestamps across the FIFO
Just want to throw this out there because it seems relevant:
http://gnuradio.org/cgit/jblum.git/tree/gruel/src/include/gruel/high_res_timer.h?h=wip/high_res_timerid=71b911d28a391ad0c67540e3658a6680d7449e1f
On 05/28/2011 02:42 PM, Alexander Chemeris wrote:
On Sat, May 28, 2011 at 22:06, Marcus D.
On 05/28/2011 06:28 PM, Josh Blum wrote:
Just want to throw this out there because it seems relevant:
http://gnuradio.org/cgit/jblum.git/tree/gruel/src/include/gruel/high_res_timer.h?h=wip/high_res_timerid=71b911d28a391ad0c67540e3658a6680d7449e1f
Yup, I know about clock_gettime().
But
On 05/28/2011 04:28 PM, Alexander Chemeris wrote:
So, while this method is simple and good for non-realtime
applications, it doesn't fit our needs. It may be usable for PHY-MAC
interaction, but even here I'm not sure it would work well.
PS I test on Core 2 Duo 1.6 GHz with all the GUI stuff
14 matches
Mail list logo
