Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Matt Mackall
On Sun, Dec 16, 2007 at 07:38:14PM +0100, Eric Dumazet wrote: > Adrian Bunk a ??crit : > >On Sun, Dec 16, 2007 at 06:42:57PM +0100, Eric Dumazet wrote: > >>Adrian Bunk a ??crit : > >>... > >>>And even more funny, with gcc 4.2 and CONFIG_CC_OPTIMIZE_FOR_SIZE=y your > >>>patch doesn't seem to make

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 07:38:14PM +0100, Eric Dumazet wrote: > > I am using gcc-4.2.1 > > CONFIG_CC_OPTIMIZE_FOR_SIZE=y makes no difference for me. > > $ make defconfig > $ egrep "OPTIMIZE_FOR_SIZE|CONFIG_SMP" .config > CONFIG_CC_OPTIMIZE_FOR_SIZE=y > CONFIG_SMP=y > $ make vmlinux > $ nm -v

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 06:42:57PM +0100, Eric Dumazet wrote: Adrian Bunk a écrit : ... And even more funny, with gcc 4.2 and CONFIG_CC_OPTIMIZE_FOR_SIZE=y your patch doesn't seem to make any space difference - are you using an older compiler or even worse

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 06:42:57PM +0100, Eric Dumazet wrote: > Adrian Bunk a écrit : >... >> And even more funny, with gcc 4.2 and CONFIG_CC_OPTIMIZE_FOR_SIZE=y your >> patch doesn't seem to make any space difference - are you using an older >> compiler or even worse

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Matt Mackall a écrit : On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 03:44:37PM +0100, Eric Dumazet wrote: Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Matt Mackall
On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: > While examining vmlinux namelist on i686, I noticed : > > c0581300 D random_table > c0581480 d input_pool > c0581580 d random_read_wakeup_thresh > c0581584 d random_write_wakeup_thresh > c0581600 d blocking_pool > > That means that

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 03:44:37PM +0100, Eric Dumazet wrote: > Adrian Bunk a écrit : >> On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: >>> While examining vmlinux namelist on i686, I noticed : >>> >>> c0581300 D random_table >>> c0581480 d input_pool >>> c0581580 d

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: > While examining vmlinux namelist on i686, I noticed : > > c0581300 D random_table > c0581480 d input_pool > c0581580 d random_read_wakeup_thresh > c0581584 d random_write_wakeup_thresh > c0581600 d blocking_pool > > That means that

[RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That means that the two integers random_read_wakeup_thresh and random_write_wakeup_thresh use

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Matt Mackall
On Sun, Dec 16, 2007 at 07:38:14PM +0100, Eric Dumazet wrote: Adrian Bunk a ??crit : On Sun, Dec 16, 2007 at 06:42:57PM +0100, Eric Dumazet wrote: Adrian Bunk a ??crit : ... And even more funny, with gcc 4.2 and CONFIG_CC_OPTIMIZE_FOR_SIZE=y your patch doesn't seem to make any space

[RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That means that the two integers random_read_wakeup_thresh and random_write_wakeup_thresh use

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That means that the two

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 03:44:37PM +0100, Eric Dumazet wrote: Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Matt Mackall
On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That means that the two

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 03:44:37PM +0100, Eric Dumazet wrote: Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Matt Mackall a écrit : On Sun, Dec 16, 2007 at 12:45:01PM +0100, Eric Dumazet wrote: While examining vmlinux namelist on i686, I noticed : c0581300 D random_table c0581480 d input_pool c0581580 d random_read_wakeup_thresh c0581584 d random_write_wakeup_thresh c0581600 d blocking_pool That

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 06:42:57PM +0100, Eric Dumazet wrote: Adrian Bunk a écrit : ... And even more funny, with gcc 4.2 and CONFIG_CC_OPTIMIZE_FOR_SIZE=y your patch doesn't seem to make any space difference - are you using an older compiler or even worse CONFIG_CC_OPTIMIZE_FOR_SIZE=n for

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Eric Dumazet
Adrian Bunk a écrit : On Sun, Dec 16, 2007 at 06:42:57PM +0100, Eric Dumazet wrote: Adrian Bunk a écrit : ... And even more funny, with gcc 4.2 and CONFIG_CC_OPTIMIZE_FOR_SIZE=y your patch doesn't seem to make any space difference - are you using an older compiler or even worse

Re: [RANDOM] Move two variables to read_mostly section to save memory

2007-12-16 Thread Adrian Bunk
On Sun, Dec 16, 2007 at 07:38:14PM +0100, Eric Dumazet wrote: I am using gcc-4.2.1 CONFIG_CC_OPTIMIZE_FOR_SIZE=y makes no difference for me. $ make defconfig $ egrep OPTIMIZE_FOR_SIZE|CONFIG_SMP .config CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SMP=y $ make vmlinux $ nm -v vmlinux|grep -4