linux-kernel - Re: [PATCH] module: kzalloc mod->ref

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]

Message-ID: <s5h63khei9t.wl%tiwai@suse.de>
Date:	Wed, 14 Jan 2009 21:37:18 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Valdis.Kletnieks@...edu
Cc:	Kyle McMartin <kyle@...radead.org>, rusty@...tcorp.com.au,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] module: kzalloc mod->ref

At Wed, 14 Jan 2009 14:29:08 -0500,
Valdis.Kletnieks@...edu wrote:
> 
> On Wed, 14 Jan 2009 17:25:31 +0100, Takashi Iwai said:
> 
> > We can use nr_cpu_ids instead of NR_CPUS.
> > For a machine like 4096 CPUs, such an amount of memory is like a
> > peanut :)
> 
> It's not peanuts if you're dealing with a distro kernel that's essentially
> forced to compile with NR_CPUS=<some moby integer>, but booting on a single or
> dual core system with possibly not even 1G of memory.

My suggestion above is to use nr_cpu_ids, which is the actual number
of CPUs, not a constant like NR_CPUS.


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/