[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60833] Re: [RFC] ih: new internal hash table
From:
Eric Wong <normalperson@...>
Date:
2014-02-18 20:27:06 UTC
List:
ruby-core #60833
Eric Wong <normalperson@yhbt.net> wrote: > The design is based on st, but uses linked-list of cache-sized arrays > for chaining, so it's as if each bucket is an st-packed array. Fwiw, I don't think this is a good design for our internal data structures. I'll experiment with others in a few weeks/months where the lookup node is embedded in the struct itself. It would use offsetof (via container_of macro) to get back the original object, meaning we avoid extra pointer chasing. This won't be good for things which use VALUEs as keys, but probably good for method tables. I'm not sure if we can/should change hash.c and its st.c usage, yet, due to public API compatibility.