All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duc Vianney <dvianney@us.ibm.com>
To: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
	mcao@us.ibm.com, bhartner@us.ibm.com
Subject: IPC lock patch performance improvement
Date: Mon, 05 Aug 2002 18:02:27 -0500	[thread overview]
Message-ID: <3D4F0403.B136A031@us.ibm.com> (raw)

I ran the LMbench Pipe and IPC latency test bucket against the IPC lock
patch from Mingming Cao and found the patch improves the performance of
those functions from 1% to 9%. See the attached data. The kernel under
test is 2.5.29, SMP kernel running on a 4-way 500 MHz. The data for
2.5.29s4-ipc represents the average of three runs.

                                                           Percent
                                  2.5.29s4 2.5.29s4-ipc Improvement
Pipe latency                         12.51     11.43         9%
AF_Unix sock stream latency          21.61     19.82         8%
UDP latency using localhost          36.28     35.12         3%
TCP latency using localhost          56.90     54.89         4%
RPC/tcp latency using local host    123.30    121.91         1%
RPC/udp latency using localhost      89.78     88.70         1%
TCP/IP connection cost to localhost 192.74    187.76         3%
Note: Latency is in microseconds
Note: 2.5.29s4 is the base 2.5.29 SMP kernel running on a 4-way,
2.5.29s4-ipc is the base 2.5.29 SMP kernel built with IPC lock patch.

Duc. dvianney@us.ibm.com


             reply	other threads:[~2002-08-05 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 23:02 Duc Vianney [this message]
2002-08-06 13:47 ` IPC lock patch performance improvement Hugh Dickins
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 17:08 Duc Vianney

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=3D4F0403.B136A031@us.ibm.com \
    --to=dvianney@us.ibm.com \
    --cc=bhartner@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=mcao@us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.