On Thu, Apr 23, 2009 at 9:40 PM, Eric Blossom wrote:
> Juha, thanks for the patch!
This has been applied to the trunk at revision 11000.
Johnathan
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discu
On Thu, Apr 23, 2009 at 01:15:56PM +0300, Juha Vierinen wrote:
> I have attached a patch to allow users to define the ethernet packet
> ring size. I remove the SLAB_SIZE restriction. I think gnuradio needs
> a fairly new >2.6.5 kernel anyway.
>
> Why is this needed? I challenge anyone to sample at
25 MB. Otherwise new users will have problems with overruns. Even
Firefox consumes hundreds of megabytes.
juha
-- Forwarded message --
From: Juha Vierinen
Date: Thu, Apr 23, 2009 at 11:00
Subject: Re: [Discuss-gnuradio] USRP2 eth_buffer
To: Bruce Stansby
Cc: Eric Blossom , Johnat
> ext file system is the go, with my high speed digitizer I stream 250
> MB/s (thats bytes) to a six disk raid (0) array. The raid zero is the go
> if you can afford to loose data in the unlikely event of a disk failure.
I'd guess that your high-speed digitizer has a buffer that is larger
than 25
, April 23, 2009 8:04 am
Subject: Re: [Discuss-gnuradio] USRP2 eth_buffer
To: j...@sgo.fi
Cc: "discuss-gnuradio@gnu.org" , Johnathan
Corgan
> On Wed, Apr 22, 2009 at 11:06:19PM +, Juha Vierinen wrote:
> > > Try setting your application to run using real-time scheduling
&g
On Wed, Apr 22, 2009 at 11:06:19PM +, Juha Vierinen wrote:
> > Try setting your application to run using real-time scheduling
> > priority. This is done in C++ via a call to:
> >
> > gr_enable_realtime_scheduling()
>
> I am using this.
Juha,
What kind of filesystem are you using? I've neve
> Try setting your application to run using real-time scheduling
> priority. This is done in C++ via a call to:
>
> gr_enable_realtime_scheduling()
I am using this.
> We use the Linux kernel packet ring method of receiving packets from
> sockets. This is a speed optimized method that maps memor
On Wed, Apr 22, 2009 at 1:48 PM, Juha Vierinen wrote:
> I have been trying to get 25 MHz to disk with USRP2. I am using the
> C++ interface and a five disk software raid 0 that can do about 150
> MB/s. I can easily run at 25 MHz with a simple nop_handler that only
> checks for underruns and time
Hi,
I have been trying to get 25 MHz to disk with USRP2. I am using the
C++ interface and a five disk software raid 0 that can do about 150
MB/s. I can easily run at 25 MHz with a simple nop_handler that only
checks for underruns and timestamps continuity, but when I write to
disk, I can barely d
