[#64517] Fw: Re: Ruby and Rails to become Apache Incubator Project — Tetsuya Kitahata <kitahata@99.alumni.u-tokyo.ac.jp>

What do you think? >> Ruby developers

13 messages 2014/08/23

[#64615] [ruby-trunk - Feature #10181] [Open] New method File.openat() — oss-ruby-lang@...

Issue #10181 has been reported by Technorama Ltd..

10 messages 2014/08/28
[#64616] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat() — Eric Wong <normalperson@...> 2014/08/28

I like this feature.

[#64671] Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object — SASADA Koichi <ko1@...>

Why this fix solve your problem?

9 messages 2014/08/30
[#64672] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object — SASADA Koichi <ko1@...> 2014/08/30

(2014/08/30 8:50), SASADA Koichi wrote:

[ruby-core:64637] Re: cowspace (work-in-progress)

From: SASADA Koichi <ko1@...>
Date: 2014-08-29 08:05:34 UTC
List: ruby-core #64637
(2014/08/29 4:49), Eric Wong wrote:
>> > Does mspace API supports to detect CoW breaking *writing*?
>> > Or programmer should predicate that this area is WORM area?
> Programmer must declare area as WORM area; mspace API has no special
> support for CoW, it is just a different API for private malloc pool.
> 

OK.

FYI:

I had confirmed that `perf' command (on linux) can find out which code
writes on shared memory area by detecting page fault.

And also, I wrote a small script to detect which memory page are shared
or not shared. You can find small script in:
Feature #10038: Extend ObjectSpace.dump to expose buffer addresses for
String and Array
https://bugs.ruby-lang.org/issues/10038#change-48031

-- 
// SASADA Koichi at atdot dot net

In This Thread

Prev Next