linux-kernel - Re: [PATCH] Allocate module.ref array dynamically

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Nov 2008 23:32:25 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Eric Dumazet <dada1@...mosbay.com>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Andreas Gruenbacher <agruen@...e.de>,
	Jan Blunck <jblunck@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Mike Travis <travis@....com>
Subject: Re: [PATCH] Allocate module.ref array dynamically

At Tue, 11 Nov 2008 23:15:50 +0100,
Eric Dumazet wrote:
> 
> Eric Dumazet a écrit :
> > Takashi Iwai a écrit :
> >> Hi,
> >>
> >> we found that the kernel module sizes and memory footprints
> >> grow drastically when NR_CPUS is high.  For example, with
> >> NR_CPUS=4096, SUSE kernel packages weigh over 500MB (even w/o debug
> >> info).
> >>
> >> A part of the reason is the fixed size array in struct module.
> >> The patch below fixes the problem by allocating it dynamically.
> >> With the patch, the size can go down to 20MB.
> >>
> >>
> >> Any comments/suggestions appreciated.
> >>
> > 
> > Many attempts were done on this area on the past.
> 
> Forgot to include a link to previous attempt : http://lkml.org/lkml/2008/5/15/402

Thanks, an interesting thread.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/