Nathan Ricci <firstname.lastname@example.org> wrote on 04/16/2014 02:42:09 PM:
> I was wondering what is actually allocated in the small code
> space? And are objects allocated there handled any differently than
> those in any other MarkSweepSpace?
The actual machine instructions (JITed code) for most methods (those that are not "too big", which go in a large code space).
You can find the original motivation and experiments for a separate code space described here: http://dx.doi.org/10.1145/1133956.1133980
The life time of code tends to be longer than many small objects, so there are some minor benefits to segregating it. The main benefit though is to separate code from data to avoid stumbling over odd/annoying micro-architectural "features" that can cause performance lost when code and data is tightly intermixed.