Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Hans Reiser
Adrian Bunk wrote: >On Tue, Mar 22, 2005 at 09:50:14AM -0800, Hans Reiser wrote: > > > >>All of my technical arguments on this topic were nicely obliterated by >>Andrew. The only real reason remaining (that I know of) is that I want >>to first eliminate all things which are a barrier to inclusi

Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Jörn Engel
[ Pruned Hans&co from Cc: list] On Tue, 22 March 2005 20:21:22 +0100, Adrian Bunk wrote: > > My plan is to send a patch to Andrew that unconditionally enables > 4KSTACKS for shaking out the last bugs before possibly removing > 8 kB stacks completely. In that case you might find this output rele

Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Adrian Bunk
On Tue, Mar 22, 2005 at 09:50:14AM -0800, Hans Reiser wrote: > All of my technical arguments on this topic were nicely obliterated by > Andrew. The only real reason remaining (that I know of) is that I want > to first eliminate all things which are a barrier to inclusion before > dealing with thi

Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Adrian Bunk
On Tue, Mar 22, 2005 at 07:56:05PM +0100, Jörn Engel wrote: > On Tue, 22 March 2005 18:13:40 +0100, Adrian Bunk wrote: > > > > REISER4_FS is the only option with a dependency on !4KSTACKS which is > > bad since 8 kB stacks on i386 won't stay forever. > > > > Could fix the problems with 4 kB stac

Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Jörn Engel
On Tue, 22 March 2005 19:56:05 +0100, Jörn Engel wrote: > > stackframes for call path too long (2808): Maybe I should change the output. "too long" simply means "user gave a stack limit below this value". 2808 bytes is the most expensive path for reiser4 without recursion, so my limit was 2800.

Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Jörn Engel
On Tue, 22 March 2005 18:13:40 +0100, Adrian Bunk wrote: > > REISER4_FS is the only option with a dependency on !4KSTACKS which is > bad since 8 kB stacks on i386 won't stay forever. > > Could fix the problems with 4 kB stacks? > > Running > > make checkstacks | grep reiser4 > > inside te k

Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Arjan van de Ven
On Tue, 2005-03-22 at 18:13 +0100, Adrian Bunk wrote: > Hi Hans, > > REISER4_FS is the only option with a dependency on !4KSTACKS which is > bad since 8 kB stacks on i386 won't stay forever. > > Could fix the problems with 4 kB stacks? I'd be interested to find out what the problem is as well;

Re: 2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Hans Reiser
Adrian Bunk wrote: >Hi Hans, > >REISER4_FS is the only option with a dependency on !4KSTACKS which is >bad since 8 kB stacks on i386 won't stay forever. > >Could fix the problems with 4 kB stacks? > >Running > > make checkstacks | grep reiser4 > >inside te kernel sources after compiling gives yo

2.6.12-rc1-mm1: REISER4_FS <-> 4KSTACKS

2005-03-22 Thread Adrian Bunk
Hi Hans, REISER4_FS is the only option with a dependency on !4KSTACKS which is bad since 8 kB stacks on i386 won't stay forever. Could fix the problems with 4 kB stacks? Running make checkstacks | grep reiser4 inside te kernel sources after compiling gives you hints where problems might co