From: Stefan Roscher <ossrosch@linux.vnet.ibm.com>
To: "LinuxPPC-Dev" <linuxppc-dev@ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
"OF-EWG" <ewg@lists.openfabrics.org>,
Roland Dreier <rolandd@cisco.com>
Cc: fenkes@de.ibm.com, alexschm@de.ibm.com, raisch@de.ibm.com,
stefan.roscher@qde.ibm.com
Subject: [PATCH 0/3] IB/ehca: Perfomance improvment for creation of queue pairs
Date: Tue, 21 Apr 2009 17:15:32 +0200 [thread overview]
Message-ID: <200904211715.32625.ossrosch@linux.vnet.ibm.com> (raw)
This patchset contains performance improvments for ehca driver.
It will skip code which is not necessary for userspace queue pairs
and will replace vmalloc() calls with kmalloc().
Because of this fundamental code change we will also increment the version number.
They should apply cleanly against 2.6.30 git tree.
Thanks
Stefan
next reply other threads:[~2009-04-21 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 15:15 Stefan Roscher [this message]
2009-04-21 17:33 ` [PATCH 0/3] IB/ehca: Perfomance improvment for creation of queue pairs 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=200904211715.32625.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=raisch@de.ibm.com \
--cc=rolandd@cisco.com \
--cc=stefan.roscher@qde.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).