public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 atomic_dec_and_lock() patch
Date: Wed, 10 Dec 2003 17:33:47 +0000	[thread overview]
Message-ID: <marc-linux-ia64-107107785321633@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107107082810707@msgid-missing>

Jermone,

>>>>> On Wed, 10 Dec 2003 16:37:22 +0100 (NFT), jerome.marchand@ext.bull.net said:

  Jerome> I have run a benchmark which load heavily the vfs on a 16
  Jerome> Itanium computer. When using lockmeter, I have noticed that
  Jerome> dcache_lock induce a significant contention when called from
  Jerome> dput. I observed a case in which 80% of CPUs time was used
  Jerome> in spin-wait!  The ia64 kernel waste all this time because
  Jerome> there is no ia64-specific implementation of
  Jerome> atomic_dec_and_lock() and the kernel use the generic
  Jerome> function instead.  I wrote the ia64 atomic_dec_and_lock
  Jerome> function and since dcache_lock never use more than 0.01% of
  Jerome> CPUs time and I have encountered no problem. The patch is
  Jerome> here.  Does someone know why this function was not
  Jerome> implemented before whereas it is implemented for ia32, ppc,
  Jerome> ppc64, sparc64 and alpha processors ?

Because nobody so far has demonstrated a need for it or hasn't gotten
around to it?

Could you try replacing the inline-asm with cmpxchg() function?  That
way, you won't break compilation with Intel's compiler.

	--david

  parent reply	other threads:[~2003-12-10 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 15:37 ia64 atomic_dec_and_lock() patch jerome.marchand
2003-12-10 15:44 ` Christoph Hellwig
2003-12-10 16:06 ` jerome.marchand
2003-12-10 17:33 ` David Mosberger [this message]
2003-12-11  9:58 ` jerome.marchand
2003-12-11 20:28 ` David Mosberger

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=marc-linux-ia64-107107785321633@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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