Re: [Discuss-gnuradio] gnuradio on ARM: gr_vmcircbuf_sysv_shm: shmat (3): Invalid argument

[esterhui]

> You can override it in the ~/.gnuradio/prefs/vmcircbuf_default_factory file.
> 

Thanks for the input, I can override with:

gr::vmcircbuf_mmap_shm_open_factory
or
gr::vmcircbuf_mmap_tmpfile_factory

and now things seem to work. I believe I know what happened though - the
very first time I compiled gnuradio, it was in the qemu user environment,
where gr::vmcircbuf_sysv_shm passed, this then was added to the
~/.gnuradio/prefs/vmcircbuf_default_factory file. I then NFS mount this
stuff to the Zynq processor (where sysv_shm doesn't work). The key is to
either remove ~/.gnuradio when switching between qemu (emulated
environment) and the real deal, or to override the
vmcircbuf_default_factory file.

Cheers

 - Stephan


On Tue, Aug 27, 2013 at 07:41:33AM -0700, Tom Rondeau-2 [via GnuRadio] wrote:

>
>
> On Tue, Aug 27, 2013 at 10:15 AM, Philip Balister <[hidden email]> wrote:
> > On 08/27/2013 09:58 AM, Johnathan Corgan wrote:
> >> On Tue, Aug 27, 2013 at 6:43 AM, Philip Balister <[hidden email]>wrote:
> >>
> >>
> >>> The circular buffer is going to become more and more painful as we try
> >>> to do cool stuff with Zynq.
> >>>
> >>
> >> Agree.  This was a good topic of discussion at the last hackfest in
> >> Virginia, and I expect there will be a presentation or two at GRCON13 on
> >> alternatives when dealing with FPGA and GPU offload architectures.
> >>
> >
> > In the short term, do you know which buffer allocator GNU Radio prefers
> > to use? Can we just disable the shm based one?
> >
> > Philip
> >
>
> You can override it in the ~/.gnuradio/prefs/vmcircbuf_default_factory file.
>
> Just put in there the line (with no newline):
>
> gr::vmcircbuf_createfilemapping_factory
>
>
> And that will tell the system to use that method of managing the
> circular buffers.
>
> Though it's supposed to test to see if your system can handle the
> shared memory method first before setting this prefs file. So I guess
> there's something different on the ARM that's not being tested for
> compliance here.
>
> --
> Tom
> Visit us at GRCon13 Oct. 1 - 4
> http://www.trondeau.com/grcon13
>
> _______________________________________________
> Discuss-gnuradio mailing list
> [hidden email]
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
>
> _______________________________________________
> If you reply to this email, your message will be added to the discussion below:
> http://gnuradio.4.n7.nabble.com/gnuradio-on-ARM-gr-vmcircbuf-sysv-shm-shmat-3-Invalid-argument-tp40870p43364.html
>
> To unsubscribe from gnuradio on ARM: gr_vmcircbuf_sysv_shm: shmat (3): Invalid argument, visit

--------------------------------------------------
Stephan Esterhuizen

GPS Systems Group
NASA/Jet Propulsion Lab
California Institute of Technology

4800 Oak Grove Drive
M/S: 138-212
Pasadena, CA 91109-8099

818-354-5942 [Office]
626-319-4871 [Mobile]
818-393-5115 [Fax]
--------------------------------------------------

---

View this message in context: Re: gnuradio on ARM: gr_vmcircbuf_sysv_shm: shmat (3): Invalid argument
Sent from the GnuRadio mailing list archive at Nabble.com.