caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Miles Egan <miles@caddr.com>
To: Lex Stein <stein@eecs.harvard.edu>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] comparison with C performance
Date: 01 May 2003 11:48:22 -0700	[thread overview]
Message-ID: <1051814902.25153.6.camel@car.pixar.com> (raw)
In-Reply-To: <Pine.BSF.4.51.0305011359200.64908@bowser.eecs.harvard.edu>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

On Thu, 2003-05-01 at 11:24, Lex Stein wrote:
> Yes, there will be additional context switch costs for a user-land
> implementation. However, where a disk I/O costs a luxury yacht a context
> switch might cost a used bicycle. So I think filesystem designers are in
> the position of not worrying about the old bike because it's best to focus
> negotiating efforts on the yacht. So I guess the question on our mind was;
> is OCaml another luxury yacht?

Your basic argument is reasonable, but I seem to remember one of the
main reasons the previously userland Linux nfs server implementation was
rewritten as a kernel-space server was to improve performance.

Perhaps it's because the typical nfs server serves most of its pages out
of its ram cache so context switches becomes more of an issue?

Anyway, drifting off-topic for this list.

-- 
Miles Egan <miles@caddr.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-05-01 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 15:27 [Caml-list] OT: Java Performance Brian Hurt
2003-05-01 17:29 ` [Caml-list] comparison with C performance Lex Stein
2003-05-01 17:55   ` Miles Egan
2003-05-01 18:24     ` Lex Stein
2003-05-01 18:48       ` Miles Egan [this message]
2003-05-01 18:38     ` Lex Stein
2003-04-27 19:04       ` Chet Murthy
2003-05-01 19:08       ` Brian Hurt
2003-05-01 19:13   ` Eray Ozkural
2003-05-02  6:02 Gregory Morrisett

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=1051814902.25153.6.camel@car.pixar.com \
    --to=miles@caddr.com \
    --cc=caml-list@inria.fr \
    --cc=stein@eecs.harvard.edu \
    /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).