All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: "Santos, Jose Renato G" <joserenato.santos@hp.com>,
	xen-devel@lists.xensource.com
Cc: Yoshio Turner <yoshiotu@hpl.hp.com>,
	Jose Renato Santos <jsantos@hpl.hp.com>,
	G John Janakiraman <john@arivalai.hpl.hp.com>
Subject: Re: [PATCH] Reduce overhead in find_domain_by_id() [0/2]
Date: Wed, 06 Dec 2006 08:43:32 +0000	[thread overview]
Message-ID: <C19C3334.56DF%keir@xensource.com> (raw)
In-Reply-To: <08CA2245AFCF444DB3AC415E47CC40AF50830E@G3W0072.americas.hpqcorp.net>

On 6/12/06 1:35 am, "Santos, Jose Renato G" <joserenato.santos@hp.com>
wrote:

> 
> This is a set of patches to improve performance of find_domain_by_id().
> find_domain_by_id shows up high in profiles for network I/O intensive
> workloads.
> Most of the cost for this function comes from 3 main functions (of
> aproximate equal costs): 1)read_lock(), 2)read_unlock() and
> 3)get_domain().
> These patches replace the lock used for accessing domain_list and
> domain_hash with a lock free RCU scheme. Experiments confirm that the
> cost of find_domain_by_id() is in fact reduced by 2/3.
> The patches apply cleanly to changeset 12732.

Do you have numbers for performance improvement on a macro benchmark?

 -- Keir

  reply	other threads:[~2006-12-06  8:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06  1:35 [PATCH] Reduce overhead in find_domain_by_id() [0/2] Santos, Jose Renato G
2006-12-06  8:43 ` Keir Fraser [this message]
2006-12-06 10:41 ` Emmanuel Ackaouy
2006-12-07  4:07   ` Santos, Jose Renato G
  -- strict thread matches above, loose matches on Subject: below --
2006-12-06 11:52 Apparao, Padmashree K
2006-12-06 12:12 ` Keir Fraser
2006-12-07  3:49   ` Santos, Jose Renato G
2006-12-07 12:01     ` Keir Fraser
2006-12-08  4:17       ` Santos, Jose Renato G

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=C19C3334.56DF%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=john@arivalai.hpl.hp.com \
    --cc=joserenato.santos@hp.com \
    --cc=jsantos@hpl.hp.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yoshiotu@hpl.hp.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.