From: "Markus Mottl" <markus.mottl@gmail.com>
To: "Berke Durak" <berke.durak@gmail.com>
Cc: yminsky@gmail.com, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Core has landed
Date: Sun, 4 May 2008 21:44:02 -0400 [thread overview]
Message-ID: <f8560b80805041844r398c88fcu1cad8fd133293dfd@mail.gmail.com> (raw)
In-Reply-To: <b903a8570805030107k9a49cc6u193719f21316c768@mail.gmail.com>
2008/5/3 Berke Durak <berke.durak@gmail.com>:
> - Bigstring: I guess those are more for I/O. The 16MB limit is not a
> problem on 64-bit arhictectures.
Right. With Bigstrings it is not necessary to blit buffers
before/after performing I/O-system calls. They also do not have to
(cannot) be moved around during heap compaction. They also play
nicely with OCaml standard I/O-channels, using vector I/O to send data
buffered by the channel and in the bigstring in one system call.
> - POLL and NODELAY in Linux_ext: that's very welcome.
Note that we support epoll in the Linux extension library, i.e. this
allows you to scale your applications to thousands of descriptors.
Regards,
Markus
--
Markus Mottl http://www.ocaml.info markus.mottl@gmail.com
next prev parent reply other threads:[~2008-05-05 1:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 21:39 Yaron Minsky
2008-05-02 23:40 ` [Caml-list] " Shivkumar Chandrasekaran
2008-05-02 23:51 ` Yaron Minsky
2008-05-03 8:07 ` Berke Durak
2008-05-03 8:22 ` Richard Jones
2008-05-03 8:54 ` Berke Durak
2008-05-03 9:08 ` Richard Jones
2008-05-03 9:18 ` David Teller
2008-05-03 9:50 ` Stefano Zacchiroli
2008-05-03 10:27 ` Daniel Bünzli
2008-05-03 15:42 ` Stefano Zacchiroli
2008-05-03 16:51 ` Sylvain Le Gall
2008-05-03 17:24 ` [Caml-list] " Daniel Bünzli
[not found] ` <b903a8570805030214i2c3a39a7t442209514f8df3a@mail.gmail.com>
2008-05-03 9:47 ` Richard Jones
2008-05-03 10:17 ` Berke Durak
2008-05-03 10:55 ` Yaron Minsky
2008-05-05 1:44 ` Markus Mottl [this message]
2008-05-05 1:36 ` Markus Mottl
2008-05-03 8:19 ` Richard Jones
2008-05-03 10:56 ` Yaron Minsky
2008-05-03 15:10 ` Ashish Agarwal
2008-05-03 16:21 ` Ralph Douglass
2008-05-05 2:22 ` Markus Mottl
2008-05-06 20:38 ` Ashish Agarwal
2008-05-06 21:02 ` Markus Mottl
2008-05-09 12:17 ` Stefano Zacchiroli
2008-05-15 12:27 ` Richard Jones
2008-05-15 12:40 ` Stefano Zacchiroli
2008-05-15 15:59 ` Markus Mottl
2008-05-15 16:03 ` Markus Mottl
2008-05-15 19:06 ` Richard Jones
2008-05-16 10:16 ` Richard Jones
2008-05-16 17:36 ` Markus Mottl
2008-05-05 2:14 ` Markus Mottl
2008-05-05 6:42 ` Stefano Zacchiroli
2008-05-05 15:01 ` Markus Mottl
2008-05-03 8:21 ` Richard Jones
2008-05-03 21:02 ` Dmitry Bely
2008-05-03 21:37 ` Richard Jones
2008-05-03 23:27 ` Yaron Minsky
2008-05-07 5:10 ` Erick Tryzelaar
2008-05-07 13:37 ` Yaron Minsky
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=f8560b80805041844r398c88fcu1cad8fd133293dfd@mail.gmail.com \
--to=markus.mottl@gmail.com \
--cc=berke.durak@gmail.com \
--cc=caml-list@inria.fr \
--cc=yminsky@gmail.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