From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] LOCK XADD for i386 incref/decref
Date: Wed, 28 Apr 2010 23:46:24 -0300 [thread overview]
Message-ID: <q2r32d987d51004281946pb3b6455dse08ddcfa389e2cdd@mail.gmail.com> (raw)
In-Reply-To: <s2q32d987d51004281939pc251a095tf1d2c481a93e00be@mail.gmail.com>
sorry for the noise, I should rest a bit after this
On Wed, Apr 28, 2010 at 11:39 PM, Federico G. Benavento
<benavento@gmail.com> wrote:
> sorry, but why in the compiler and not as a library function like in libthread?
>
> http://plan9.bell-labs.com/sources/plan9/sys/src/libthread/xinc386.s
>
> On Wed, Apr 28, 2010 at 4:16 PM, Venkatesh Srinivas
> <me@endeavour.zapto.org> wrote:
>> Hi,
>>
>> A few months ago, I added a patch to inferno-npe to use LOCK XADD
>> instead of the current lock/add/unlock sequence for incref and decref:
>> (http://code.google.com/p/inferno-npe/source/detail?r=b83540e1e77e62a19cbd21d2eb54d43d338716a5
>> and http://code.google.com/p/inferno-npe/source/detail?r=82f13e6755218ecb7dec0f1392b2eb8bfe0bb2c7).
>> On a 2.66 GHz Core 2 Duo, we noticed a full 14% reduction in runtime
>> (9.6s vs 11.2s) of the thread-ring test. Similar performance gains
>> were noticed on a Core i7 machine, but I no longer have the numbers
>> handy.
>>
>> Perhaps this change is interesting for Plan 9...
>>
>> -- vs
>>
>>
>
>
>
> --
> Federico G. Benavento
>
--
Federico G. Benavento
next prev parent reply other threads:[~2010-04-29 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <r2zf75780241004281003ua9c23045xc4831f3735477989@mail.gmail.com>
2010-04-28 19:16 ` Venkatesh Srinivas
2010-04-29 2:39 ` Federico G. Benavento
2010-04-29 2:46 ` Federico G. Benavento [this message]
2010-09-07 19:48 ` erik quanstrom
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=q2r32d987d51004281946pb3b6455dse08ddcfa389e2cdd@mail.gmail.com \
--to=benavento@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).