[#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:64614] cowspace (work-in-progress)

From: Eric Wong <normalperson@...>
Date: 2014-08-28 21:10:01 UTC
List: ruby-core #64614
Hi all, I started working on a cowspace branch.  Based on the mspace API
of new versions of dlmalloc.   The idea is to have a separate malloc
space for long-lived, WORM (write once, read many) data which may
increase memory sharing for forked processes.

The mspace API is similar to normal malloc:

	malloc(size) => mspace_malloc(GET_VM()->cowspace, size)
	free(ptr) => mspace_free(GET_VM()->cowspace, ptr)
	...

There are rb_cow_(malloc/free/...) function wrappers as well
as COW_(ALLOC/ZALLOC) macros to ease migrations.

However, I haven't found any benefits, yet.  _Maintaining_
CoW-friendliness is difficult in long-term so it might not be worth it
(compared to overall memory reductions).

http://bogomips.org/ruby.git/log/?h=cowspace
(git clone git://bogomips.org/ruby.git / branch: cowspace)

In This Thread

Prev Next