Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc List <linux-parisc@vger.kernel.org>,
	Helge Deller <deller@gmx.de>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH] parisc: Improve LWS-CAS performance
Date: Mon, 12 May 2014 08:11:37 +0200	[thread overview]
Message-ID: <5283741.MSteB7R1e7@caliban.sf-tec.de> (raw)
In-Reply-To: <BLU0-SMTP178D56FBECCDEE0B3D0BE6974A0@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

Am Sonntag, 11. Mai 2014, 18:40:50 schrieb John David Anglin:
> The attached change significantly improves the performance of the LWS-
> CAS code in syscall.S.
> This allows a number of packages to build (e.g., zeromq3, gtest and
> libxs) that previously failed because
> slow LWS-CAS performance under contention.  In particular, interrupts
> taken while the lock was taken
> degraded performance significantly.

Sounds cool ;)

The label cas_wouldblock would now only be defined in SMP case, which looks 
odd. Since I can't find any references to it I think it should just be dropped.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-05-12  6:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 22:40 [PATCH] parisc: Improve LWS-CAS performance John David Anglin
2014-05-12  6:11 ` Rolf Eike Beer [this message]
2014-05-12 14:33   ` John David Anglin
2014-05-12 15:04     ` Aw: " Helge Deller
2014-05-14  3:31 ` Carlos O'Donell
2014-05-14 19:12   ` Helge Deller
2014-05-14 19:28     ` John David Anglin
2014-05-15 12:33   ` [PATCH] parisc: Improve LWS-CAS performance (take 2) John David Anglin

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=5283741.MSteB7R1e7@caliban.sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=linux-parisc@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