Should we obsolete "memorysize" in FlightRecorderOptions?

[Denghui Dong]

Hi team,

I notice that JfrMemorySpace::_limit_size is never used(maybe I'm wrong),
and _limit_size of _global_mspace will use the value of "memorysize"(default 10m) in FlightRecorderOptions.

Should we obsolete it or use it to limit the max size of JfrMemorySpace? 
I'm worried that users think they can use "memorysize" to control the size of memory to be used by JFR, but actually they can't.

is it right?

Thanks,
Denghui Dong