caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vitaly Lugovsky <vsl@ontil.ihep.su>
To: Vikas Sodhani <vikas_sodhani@oryxa.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml and linux kernel programming
Date: Sat, 3 Nov 2001 23:55:13 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.33.0111032347570.20684-100000@ontil.ihep.su> (raw)
In-Reply-To: <3BE2B882.2D176F44@oryxa.com>

On Fri, 2 Nov 2001, Vikas Sodhani wrote:

> Hi, I am just learning the OCaml language and was hoping to receive some
> advice on the possibilities and trade offs of writing linux kernel
> modules using ocaml. 

 You can try userspace system call gateway (don't remember the name of 
this patch... Winmodem people are playing with it right now, so you can
ask them).

> I am trying to write a module that sits in between the file system and a
> hard disk device driver.  The code would interpret the calls from the
> file system and relay calls back to the hard disk device driver. 
> Essentially the code would be a layer over the hard disk device driver.

 Kernel space modules are very limited. :(

> Is this possible using OCaml?  What are the trade offs of using ocaml
> versus c.  I would appreciate any advice or help.

 Btw., 2ALL: what about "Caml OS"? It can be a binfmt-misc module for 
Linux, and even an infrastructure for a syscall gateway for Caml kernel
drivers.


-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-11-03 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 15:15 Vikas Sodhani
2001-11-03 20:55 ` Vitaly Lugovsky [this message]
2001-11-05 10:06 ` Xavier Leroy
  -- strict thread matches above, loose matches on Subject: below --
2001-09-05  9:33 Ohad Rodeh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.33.0111032347570.20684-100000@ontil.ihep.su \
    --to=vsl@ontil.ihep.su \
    --cc=caml-list@inria.fr \
    --cc=vikas_sodhani@oryxa.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).