From: "Ohad Rodeh" <ORODEH@il.ibm.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml and linux kernel programming
Date: Wed, 5 Sep 2001 12:33:36 +0300 [thread overview]
Message-ID: <OFAF89CD54.CE551A68-ONC2256ABE.003442CB@telaviv.ibm.com> (raw)
Mark Hayden wrote a kernel module in Ocaml, he posted a message on this
topic
about two years ago. The major problem was memory allocation in a
different
segement using the Caml GC.
Look it up, perhaps it will be of value to you.
Ohad.
Xavier Leroy <xavier.leroy@inria.fr>@pauillac.inria.fr on 05/11/2001
12:06:04
Please respond to Xavier Leroy <xavier.leroy@inria.fr>
Sent by: owner-caml-list@pauillac.inria.fr
To: Vikas Sodhani <vikas_sodhani@oryxa.com>
cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml and linux kernel programming
> 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.
As Vitaly said, your best bet is to run the Caml code in user space
via some sort of kernel/userland gateway. Kernel-land is a somewhat
restricted programming environment. E.g. you can't even write kernel
code in (full) C++ because the run-time environment for C++
allocations and exceptions is not available in the kernel. So, your
chances of getting OCaml code to run in the kernel are very slim :-)
- Xavier Leroy
-------------------
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
-------------------
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
next reply other threads:[~2001-11-05 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 9:33 Ohad Rodeh [this message]
2001-11-02 15:15 Vikas Sodhani
2001-11-03 20:55 ` Vitaly Lugovsky
2001-11-05 10:06 ` Xavier Leroy
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=OFAF89CD54.CE551A68-ONC2256ABE.003442CB@telaviv.ibm.com \
--to=orodeh@il.ibm.com \
--cc=caml-list@inria.fr \
/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).