linux-kernel - Re: [PATCH 1/3] IB/ehca: Replace vmalloc with kmalloc

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:	Wed, 22 Apr 2009 18:00:41 +0200
From:	Stefan Roscher <ossrosch@...ux.vnet.ibm.com>
To:	michael <michael@...dence.eu.com>
Cc:	Roland Dreier <rdreier@...co.com>, fenkes@...ibm.com,
	LKML <linux-kernel@...r.kernel.org>,
	"OF-EWG" <ewg@...ts.openfabrics.org>,
	"LinuxPPC-Dev" <linuxppc-dev@...abs.org>, raisch@...ibm.com,
	alexschm@...ibm.com, stefan.roscher@...ibm.com
Subject: Re: [PATCH 1/3] IB/ehca: Replace vmalloc with kmalloc

On Wednesday 22 April 2009 04:10:18 pm michael wrote:
> Hi,
> 

> I don't take the point, if it is not import use the vmalloc. Why you try 
> with a kmalloc
> alloc first? and why do not use kzalloc?

Because kmalloc() is faster than vmalloc() causing a huge performance win
when someone allocates a large number of queue pairs. We fall back to
vmalloc() only if kmalloc() can't deliver the memory chunk.
We don't need kzalloc because we fill the list right after the alloc.

regards Stefan

--
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/