From: Zheng Li <li@pps.jussieu.fr>
To: caml-list@inria.fr
Subject: Re: [ANN] coThreads 0.10
Date: Tue, 18 Sep 2007 11:01:02 +0200 [thread overview]
Message-ID: <87y7f473g1.fsf@pps.jussieu.fr> (raw)
In-Reply-To: <20070918162347.e04ac421.mle+ocaml@mega-nerd.com>
Hi,
Erik de Castro Lopo <mle+ocaml@mega-nerd.com> writes:
> skaller wrote:
>
>> But it isn't an errno value that is reported, it is the index
>> of the variant that is 12, and that is "Invalid Argument".
>
> Ok.
>
>> It is not clear that a seek to an invalid position in the file
>> is going to succeed. It's also not clear to me that the seek
>> argument isn't 32 bits (depends on complex ugly GNU macro
>> hackery what type off_t is .. my Caml got built with
>> the LARGE_FILE macro thing so it should be 64 bits).
>
> Shouldn't off_t always be 64 bits on a 64 bit CPU? I only see
> this problem on x86-64 and Sys.word_size is 64.
Thank you for the bug report.
Unfortunately I don't have a x64 machine to test, and know quite little about
64bit machine (that's why I made the mistake).
But the bug reason seems obvious: on a x64 machine, one have to use
Unix.LargeFile.lseek to seek the address in the extra space.
On the other hand, I think 2^14 locks (the x86 case) are fairly enough in
most situation. So we don't have to bother with Int64 and LargeFile. Could you
(or anyone else with a x64 machine) help to test the simple solution: change
"Sys.word_size - 2" in the definition of "fresh_number" to
"(min Sys.word_size 32) - 2" as follows
let fresh_number =
let usable_size = (min Sys.word_size 32) -2 in
let bits_of_id = 16 in (* Should be sufficient in most OS *)
........
and report whether it works? Thanks
--
Zheng Li
http://www.pps.jussieu.fr/~li
next prev parent reply other threads:[~2007-09-18 8:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 16:31 Zheng Li
2007-09-17 16:48 ` Zheng Li
2007-09-17 17:39 ` [Caml-list] " skaller
2007-09-17 17:51 ` Zheng Li
2007-09-17 21:33 ` [Caml-list] " skaller
2007-09-17 22:37 ` Zheng Li
2007-09-17 23:26 ` [Caml-list] " skaller
2007-09-18 0:16 ` Zheng Li
2007-09-18 0:53 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 1:25 ` Erik de Castro Lopo
2007-09-18 4:29 ` skaller
2007-09-19 10:11 ` Erik de Castro Lopo
2007-09-19 10:58 ` Can coThreads be used for message passing architecture? Jan Kybic
2007-09-19 11:13 ` [Caml-list] " Erik de Castro Lopo
2007-09-19 12:59 ` Zheng Li
2007-09-20 4:16 ` [Caml-list] " Jon Harrop
2007-09-20 6:11 ` Erik de Castro Lopo
2007-09-20 9:06 ` Zheng Li
2007-09-20 8:49 ` Zheng Li
2007-09-19 19:13 ` [Caml-list] Re: [ANN] coThreads 0.10 Vu Ngoc San
2007-09-19 20:10 ` Zheng Li
2007-09-20 0:50 ` [Caml-list] " skaller
2007-09-20 4:29 ` Erik de Castro Lopo
2007-09-20 7:11 ` skaller
2007-09-20 7:52 ` Erik de Castro Lopo
2007-09-20 8:37 ` Zheng Li
2007-09-20 10:43 ` [Caml-list] " skaller
2007-09-20 10:44 ` Matthew Hannigan
2007-09-20 15:02 ` skaller
2007-09-20 15:07 ` Christophe Raffalli
2007-09-20 15:51 ` skaller
2007-09-20 16:26 ` Florian Weimer
2007-09-20 17:37 ` Vincent Aravantinos
2007-09-21 16:33 ` readline license (was: [ANN] coThreads 0.10) Xavier Leroy
2007-09-21 17:11 ` [Caml-list] " Matthew William Cox
2007-09-21 18:05 ` skaller
2007-09-21 21:51 ` [Caml-list] Re: readline license Markus E L
2007-09-21 22:16 ` Daniel Bünzli
2007-09-22 0:49 ` [Caml-list] Re: readline license (was: [ANN] coThreads 0.10) Matthew Hannigan
2007-09-20 11:39 ` [Caml-list] Re: [ANN] coThreads 0.10 Florian Weimer
2007-09-20 15:46 ` skaller
2007-09-20 18:14 ` Ken Rose
2007-09-20 8:31 ` Zheng Li
2007-09-20 8:18 ` Zheng Li
2007-09-18 2:10 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 5:59 ` skaller
2007-09-18 6:23 ` Erik de Castro Lopo
2007-09-18 9:01 ` Zheng Li [this message]
2007-09-18 13:40 ` Zheng Li
2007-09-18 23:53 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 9:09 ` [Caml-list] " skaller
2007-09-18 13:03 ` Markus E L
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=87y7f473g1.fsf@pps.jussieu.fr \
--to=li@pps.jussieu.fr \
--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