>> I don't think we should export vm_stack. It's purely implementation
>> detail. Just expose "stack size"
>> knob and it should change both vm-stack and machine-stack size.
> You're right. It's better to provide more abstract way to tune memory usa=
ge of Fiber.
> How about like the following?
>
> =A0Fiber.stacksize =3D 2.0 =A0# =3D> twice the size of default stack size
>
> or maybe we have to examine how VM/machine stack are consumed.
>
> And even tough we provide such a unified interface, I think more low-leve=
l,
> implementation specific methods are convenient when users need fine-tuned=
 parameter set for
> their applications. Is it a bad idea?
> for example, ObjectSpace.count_objects etc.. tightly depend on MRI implem=
entation,
> and are useful just because of it.

Luke, use 64bit. Stack size should be enough large by default. Tuning
knob request often
point out a bad default value. Theoretically, thread class has the
same issue but we haven't
got a bug report and implemented the knob. It seems implies the root
cause is in default value.

Thanks.