From: Stefan Roscher <ossrosch@linux.vnet.ibm.com>
To: michael <michael@evidence.eu.com>
Cc: Roland Dreier <rdreier@cisco.com>,
fenkes@de.ibm.com, LKML <linux-kernel@vger.kernel.org>,
OF-EWG <ewg@lists.openfabrics.org>,
LinuxPPC-Dev <linuxppc-dev@ozlabs.org>,
raisch@de.ibm.com, alexschm@de.ibm.com,
stefan.roscher@de.ibm.com
Subject: Re: [PATCH 1/3] IB/ehca: Replace vmalloc with kmalloc
Date: Wed, 22 Apr 2009 18:00:41 +0200 [thread overview]
Message-ID: <200904221800.41399.ossrosch@linux.vnet.ibm.com> (raw)
In-Reply-To: <49EF254A.6020106@evidence.eu.com>
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
next prev parent reply other threads:[~2009-04-22 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 15:16 [PATCH 1/3] IB/ehca: Replace vmalloc with kmalloc Stefan Roscher
2009-04-21 17:34 ` Roland Dreier
2009-04-22 9:11 ` Stefan Roscher
2009-04-22 14:02 ` Stefan Roscher
2009-04-22 14:10 ` michael
2009-04-22 16:00 ` Stefan Roscher [this message]
2009-04-22 16:12 ` michael
2009-04-28 13:07 ` [ewg] " Alexander Schmidt
2009-04-28 14:01 ` Roland Dreier
2009-04-28 14:13 ` Alexander Schmidt
2009-04-28 15:12 ` Dave Hansen
2009-04-28 16:02 ` Stefan Roscher
2009-04-28 16:45 ` Roland Dreier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904221800.41399.ossrosch@linux.vnet.ibm.com \
--to=ossrosch@linux.vnet.ibm.com \
--cc=alexschm@de.ibm.com \
--cc=ewg@lists.openfabrics.org \
--cc=fenkes@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@evidence.eu.com \
--cc=raisch@de.ibm.com \
--cc=rdreier@cisco.com \
--cc=stefan.roscher@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).