[okl4-developer] Using naming and IPC from within OK-linux

[Jorge Torres]

Hi,

I dont see why you couldnt write to your proc driver.
On your  mp_init_module function

Our_Proc_File = create_proc_entry(PROC_ENTRY_FILENAME, 0644, NULL);
Our_Proc_File->proc_fops = &File_Ops_4_Our_Proc_File;

-----
static struct file_operations File_Ops_4_Our_Proc_File = {
    .read      = procfs_read,
    .write      = procfs_write,
    .open      = procfs_open,
    .release = procfs_close,
};

-------

and you could code somethig at open, write, etc

int procfs_open(struct inode *inode, struct file *file)
{
   your L4 IPC code
}

Cheers,

Jorge



On Feb 19, 2008 5:45 PM, Subcommander l0r3zz <l0r3zz at gmail.com> wrote:

>
>
> On Feb 19, 2008 2:01 PM, Jorge Torres <jorge.torres.maldonado at gmail.com>
> wrote:
>
> > Hi Geoff,
> >
> > I have done; A Linux syscall that proxies IPC calls and a proc driver,
> > what I experienced was that the driver is a better approach, plus syscalls
> > will mess up your compiler and you will have to port them to every
> > architecture, if you want I will search and post a code for you, the ideal
> > thing would be to have auto-generated studs for each service you provide on
> > iguana, that is something Ben
> >
> > Hope it helps,
> >
> > Jorge
> >
>
>
> Hmmm, I have a very simple /proc driver that just list out the KIP for
> now. and I was thinking how to extend it. I could add a char driver
> implementation, but then doesn't IPC look more like a block device, or
> really even a network device?  I guess one advantage to a char driver is
> that then you can write userland PERL, Scheme and Ruby programs that could
> talk to Iguana Servers very easily.
>
>
>
> Did your /proc driver allow userland threads to write into parts of it?
> I'm just curious how you went about it?
>
> >
> >
> >
> >
> > On Feb 19, 2008 3:36 PM, Geoff White <netengadmin at gmail.com> wrote:
> >
> > >
> > >
> > > On Feb 19, 2008 12:15 PM, Jorge Torres <
> > > jorge.torres.maldonado at gmail.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > Write a Linux driver, which searches on the naming service for the
> > > > thread ID you registered, and sends it back to the linux thread,
> > > >
> > > > Cheers,
> > > >
> > > > Jorge
> > > >
> > >
> > >
> > > Jorge,
> > > Have you written such a driver?
> > > Is it a char device or block or network?
> > > I was thinking of trying to make a more universal type of driver
> > > interface to the L4 IPC mechanism but was thinking that the real way
> > > to do it was to extend the existing Linux IPC mechanism to accommodate
> > > L4 IPC.
> > >
> > > What do you think?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > >
> > > >
> > > > On Feb 19, 2008 1:14 PM, Damien Schulz <damien.schulz at 4xtc.de>
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I'm writing a client application for ok-linux that should be able
> > > > > to communicate with a l4 service via IPC. The service registers itself at
> > > > > the naming service to share its thread id with the client application.
> > > > > Unfortunately the linux client isn't able too lookup anything from the
> > > > > naming service and alway crashes with a segmentation fault. So is it
> > > > > poosible to resolve a name from within an OK-linux application? And if yes,
> > > > > how is it possible? Is it futhermore possible to use magpie generated code
> > > > > from within a wombat application to communicate with a l4 based service?
> > > > >
> > > > > Thank you,
> > > > >  ~Damien
> > > > >
> > > > > _______________________________________________
> > > > > Developer mailing list
> > > > > Developer at okl4.org
> > > > > https://lists.okl4.org/mailman/listinfo/developer
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Developer mailing list
> > > > Developer at okl4.org
> > > > https://lists.okl4.org/mailman/listinfo/developer
> > > >
> > > >
> > >
> >
> > _______________________________________________
> > Developer mailing list
> > Developer at okl4.org
> > https://lists.okl4.org/mailman/listinfo/developer
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080219/931c030a/attachment-0001.htm