public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Threads, inelegance, and Java
Date: Wed, 20 Jun 2001 21:10:08 -0700	[thread overview]
Message-ID: <3B3173A0.F244EF5B@kegel.com> (raw)

Russell Leighton wrote:
> The lack of a good operating system _dependent_ interface
> makes running fast hard in Java when you need to do IO...
> yes, there is always JNI so you can add a little C to mmap a file or whatever,

JDK 1.4 beta comes with a way to memory-map files, and various
other I/O improvements (like poll(); see http://www.jcp.org/jsr/detail/51.jsp).
Chris Smith will have some nio benchmarks up on http://www.jlinux.org/
next week or so showing how well their nonblocking network I/O performs.

Sun is slowly getting their act together on the I/O front with java.
Still, the competition from C# and for that matter gcj will probably be 
a good thing, keep 'em on their toes.

(Disclaimer: I served on the JSR-51 expert group, representing the linux 
point of view, kinda.)
- Dan

             reply	other threads:[~2001-06-21  4:08 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21  4:10 Dan Kegel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-20 21:13 [OT] Threads, inelegance, and Java Holzrichter, Bruce
2001-06-20 21:17 ` Richard B. Johnson
2001-06-20  9:00 Alan Cox quote? (was: Re: accounting for threads) Henning P. Schmiedehausen
2001-06-20 11:25 ` [OT] Threads, inelegance, and Java Aaron Lehmann
2001-06-20 11:25   ` Rob Landley
2001-06-20 17:36     ` Martin Dalecki
2001-06-20 19:27       ` Mike Harrold
2001-06-20 17:46         ` Rob Landley
2001-06-20 19:53         ` Martin Dalecki
2001-06-20 17:53           ` Rob Landley
2001-06-21  7:45             ` Albert D. Cahalan
     [not found]         ` <mailman.993067219.29993.linux-kernel2news@redhat.com>
2001-06-20 20:16           ` Pete Zaitcev
2001-06-20 22:05             ` Alan Cox
     [not found]     ` <20010621000725.A24672@werewolf.able.es>
2001-06-20 19:15       ` Rob Landley
2001-06-21  9:40         ` Jonathan Morton
     [not found]       ` <mailman.993083762.1429.linux-kernel2news@redhat.com>
2001-06-21  3:13         ` Pete Zaitcev
2001-06-21 13:59           ` Rob Landley
2001-06-21 16:48     ` Adam Sampson
2001-06-20 15:12   ` Ben Greear
2001-06-20 15:44     ` Russell Leighton
2001-06-20 16:32       ` Davide Libenzi
2001-06-20 16:54         ` Russell Leighton
2001-06-20 17:03         ` Tony Hoyle
2001-06-20 15:10           ` Rob Landley
2001-06-20 20:23             ` Tony Hoyle
2001-06-21  8:12               ` Henning P. Schmiedehausen
2001-06-20 20:40             ` Richard B. Johnson
2001-06-20 20:48               ` Tony Hoyle
2001-06-20 21:00               ` Daniel Phillips
2001-06-20 21:06                 ` Richard B. Johnson
2001-06-20 18:14         ` Henning P. Schmiedehausen
2001-06-20 16:53     ` Larry McVoy
2001-06-20 12:36       ` Rob Landley
2001-06-20 21:14     ` Aaron Lehmann
2001-06-20 18:09   ` Henning P. Schmiedehausen
2001-06-20 19:05   ` William T Wilson

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=3B3173A0.F244EF5B@kegel.com \
    --to=dank@kegel.com \
    --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