From: Peter Teoh <htmldeveloper@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>
Subject: RFC: Writing Solaris Device Drivers in Java
Date: Mon, 31 Mar 2008 10:14:55 +0800 [thread overview]
Message-ID: <47F0491F.4050804@gmail.com> (raw)
Interesting read:
http://research.sun.com/techrep/2006/smli_tr-2006-156.pdf
Personal comments:
Since KVM and Xen/OpenVZ etc other virtual machines are beginning to pop
up - I don't see why it inhibits (in spite of the many initial
difficulties as mentioned in the paper) the growth of using Java for
device drivers development. Contrast it against udev - esp in terms of
usability/supportability/extensibility etc. udev is a Linux thing,
whereas Java is at industry level. If everyone write applications
device drivers using Java (minus the extreme hardware arch specific
stuff, but supports all the low level protocol specific stuff like
TCP/IP, NFS, USB etc) then I think it has potential to compete against C
lang - the monopolizer till today in the kernel world
(Windows/MacOS/Linux/BSD etc). Ie, imagine using a drivers written for
the Solaris in Linux, won't it be cool?
next reply other threads:[~2008-03-31 2:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 2:14 Peter Teoh [this message]
2008-03-31 2:59 ` RFC: Writing Solaris Device Drivers in Java Bernd Eckenfels
2008-03-31 3:13 ` Al Viro
2008-03-31 15:18 ` Peter Teoh
2008-03-31 15:52 ` Peter Teoh
2008-03-31 16:20 ` Ioan Ionita
2008-03-31 3:10 ` David Miller
2008-03-31 5:56 ` Willy Tarreau
2008-03-31 8:48 ` David Newall
2008-03-31 8:12 ` Benjamin Herrenschmidt
2008-03-31 10:28 ` Peter Zijlstra
2008-03-31 10:45 ` Wander Winkelhorst
2008-03-31 11:58 ` Jacek Luczak
2008-03-31 14:54 ` Peter Teoh
2008-04-01 12:51 ` Daniel Bonekeeper
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=47F0491F.4050804@gmail.com \
--to=htmldeveloper@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
/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