IBM java: Turning on SMP seems more and more likely the key
billfink at mindspring.com
Wed May 29 13:07:55 EST 2002
Oops, I meant to send this to linuxppc-user, but since it appears to
be a kernel issue, maybe this is an appropriate forum after all, and
maybe someone will have some ideas about what might be wrong.
The basic problem is that the IBM J2RE java software (build 1.3.1)
gets an "out of memory" error when run on a UP system with a UP
2.4.19-pre8-ben0 kernel. The current "fix" is to enable SMP, i.e.
running an SMP 2.4.19-pre8-ben0 kernel on the same UP system causes
the java code to work fine.
Note I am not running the java code myself. I was just offering some
comments on the IBM java problem as reported by several other users
(at least three users reported that enabling SMP "fixed" the IBM J2RE
java "out of memory" problem).
On Tue, 28 May 2002, Bill Fink wrote:
> On Tue May 28 2002, Graham Leggett wrote:
> > James Gunning wrote:
> > > Have just verified that toggling SMP *on* is the critical
> > > switch to get the IBM java to go.
> > Had the same result here: SMP kernel + java = works.
> > Trouble is the SMP kernel is noticably slower than the non SMP kernel on
> > non SMP systems.
> My best guess is that the bug is somewhere in /usr/src/linux/mm/slab.c
> since that is the only part of the MM code that's dependent on CONFIG_SMP.
> One difference I see is that the SMP code uses kmem_cache_alloc_batch
> which is a real function, whereas the non-SMP code uses kmem_cache_alloc_one
> which is a macro. Also the SMP code writes something to the /proc file
> system while the non-SMP code does not. But I don't see anything obviously
> wrong, although I'm certainly no expert in this area.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev