[#41916] Proposal: Bitmap Marking GC — Narihiro Nakamura <authornari@...>

Hi.

18 messages 2012/01/05

[#41941] [ruby-trunk - Bug #5851][Open] make check fails when compiling with GCC 4.7 - *** longjmp causes uninitialized stack frame *** — Vit Ondruch <v.ondruch@...>

12 messages 2012/01/06

[#41979] [ruby-trunk - Bug #5865][Open] Exception#== should return false if the classes differ — Hiro Asari <asari.ruby@...>

10 messages 2012/01/08

[#42003] [ruby-trunk - Bug #5871][Open] regexp \W matches some word characters when inside a case-insensitive character class — Gareth Adams <gareth@...>

14 messages 2012/01/09

[#42016] [ruby-trunk - Feature #5873][Open] Adopt FFI over DL — Heesob Park <phasis@...>

15 messages 2012/01/10

[#42149] [ruby-trunk - Feature #5899][Open] chaining comparsions. — Ondrej Bilka <neleai@...>

12 messages 2012/01/16

[#42164] [ruby-trunk - Feature #5903][Open] Optimize st_table (take 2) — Yura Sokolov <funny.falcon@...>

18 messages 2012/01/17

[ruby-core:42249] Re: Proposal: Bitmap Marking GC

From: Kurt Stephens <ks@...>
Date: 2012-01-27 22:02:21 UTC
List: ruby-core #42249
On 1/27/12 1:38 PM, Eric Wong wrote:
> Eric Wong <normalperson@yhbt.net> wrote:
>> A larger (16KB) _size_ I can easily understand to be more efficient.
>> I just don't see a reason for _alignment_ to be 16KB, too.  Larger
>> alignment increases the chance of fragmentation.
> 
> Btw, I took at Bug #5901 and now realize why this GC requires
> alignment to match size.  It makes mapping a VALUE back to its Ruby
> heap much easier (compared to the REE GC, which needed to scan heaps).
> 
All the more reason to use mmap() instead of malloc_aligned().
-- KAS



In This Thread

Prev Next