public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: muli@il.ibm.com
To: ak@suse.de
Cc: linux-kernel@vger.kernel.org, muli@il.ibm.com, jdmason@kudzu.us
Subject: Calgary: more updates for 2.6.23
Date: Wed, 11 Jul 2007 16:35:10 +0300	[thread overview]
Message-ID: <11841609143732-git-send-email-muli@il.ibm.com> (raw)

Hi Andi,

Here are a few more Calgary updates that are appropriate for
2.6.23. The only notable one is the second one, which tightens up the
bitmap locking to only lock where absolutely necessary, giving us a
nice 10-15% improvement in CPU utilization running netperf on a large
SMP machine. Please apply.

Thanks,
Muli


             reply	other threads:[~2007-07-11 13:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 13:35 muli [this message]
2007-07-11 13:35 ` [PATCH 1/4] x86-64: Calgary - fix few style problems pointed out by checkpatch.pl muli
2007-07-11 13:35   ` [PATCH 2/4] x86-64: Calgary - tighten up the bitmap locking muli
2007-07-11 13:35     ` [PATCH 3/4] x86-64: Calgary - fold in redundant functions muli
2007-07-11 13:35       ` [PATCH 4/4] x86_64: Calgary - change _map_single, etc to static muli

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=11841609143732-git-send-email-muli@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=ak@suse.de \
    --cc=jdmason@kudzu.us \
    --cc=linux-kernel@vger.kernel.org \
    /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