From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: akpm@osdl.org, guillaume.thouvenin@bull.net, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Re: connector is missing in 2.6.12-rc2-mm1]
Date: Fri, 08 Apr 2005 07:33:58 +0400 [thread overview]
Message-ID: <1112931238.28858.180.camel@uganda> (raw)
In-Reply-To: <E1DJjiR-000850-00@gondolin.me.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On Fri, 2005-04-08 at 12:59 +1000, Herbert Xu wrote:
> Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> >
> > atomic_dec_and_test() is more expensive than 2 barriers + atomic_dec(),
> > but in case of connector I think the price is not so high.
>
> Can you list the platforms on which this is true?
sparc64, some mips [at least in UP].
I do not know about others, but I think that any
arch, where atomic operations are serialized,
has sync/isync in atomic_dec_and_test()
and does not for atomic_dec().
> Thanks,
--
Evgeniy Polyakov
Crash is better than data corruption -- Arthur Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-08 3:27 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1112859412.18360.31.camel@frecb000711.frec.bull.fr>
2005-04-07 7:53 ` [Fwd: Re: connector is missing in 2.6.12-rc2-mm1] Evgeniy Polyakov
2005-04-07 7:58 ` Andrew Morton
2005-04-07 8:23 ` Evgeniy Polyakov
2005-04-07 8:32 ` Andrew Morton
2005-04-07 10:12 ` Evgeniy Polyakov
2005-04-08 2:59 ` Herbert Xu
2005-04-08 3:33 ` Evgeniy Polyakov [this message]
2005-04-08 3:32 ` Herbert Xu
2005-04-08 3:52 ` Evgeniy Polyakov
2005-04-08 3:50 ` Herbert Xu
2005-04-08 4:02 ` Evgeniy Polyakov
2005-04-08 4:02 ` Herbert Xu
2005-04-08 4:21 ` Evgeniy Polyakov
2005-04-08 4:17 ` Herbert Xu
2005-04-08 4:23 ` David S. Miller
2005-04-08 4:55 ` Evgeniy Polyakov
2005-04-08 4:53 ` Herbert Xu
2005-04-08 4:55 ` David S. Miller
2005-04-08 5:11 ` Evgeniy Polyakov
2005-04-08 5:08 ` Herbert Xu
2005-04-08 5:19 ` Evgeniy Polyakov
2005-04-08 6:02 ` David S. Miller
2005-04-08 13:11 ` Daniel Jacobowitz
2005-04-08 6:12 ` Evgeniy Polyakov
2005-04-08 4:22 ` David S. Miller
2005-04-07 8:13 ` Evgeniy Polyakov
2005-04-07 9:12 ` Ian Campbell
2005-04-07 9:52 ` Evgeniy Polyakov
2005-04-07 10:41 ` Kay Sievers
2005-04-07 11:24 ` Evgeniy Polyakov
2005-04-07 14:23 ` Kay Sievers
2005-04-07 14:49 ` Evgeniy Polyakov
2005-04-07 15:47 ` James Morris
2005-04-08 3:41 ` Evgeniy Polyakov
2005-04-08 5:55 ` James Morris
2005-04-08 6:48 ` Evgeniy Polyakov
2005-04-10 9:52 ` Herbert Xu
2005-04-10 10:32 ` Evgeniy Polyakov
2005-04-10 11:08 ` Kay Sievers
2005-04-10 11:37 ` Evgeniy Polyakov
2005-04-10 11:54 ` Evgeniy Polyakov
2005-04-10 12:10 ` Thomas Graf
2005-04-10 12:15 ` Evgeniy Polyakov
2005-04-10 14:39 ` jamal
2005-04-10 14:56 ` James Morris
2005-04-10 15:08 ` jamal
2005-04-10 19:27 ` Thomas Graf
2005-04-11 5:22 ` Evgeniy Polyakov
2005-04-11 10:45 ` Thomas Graf
2005-04-11 11:19 ` Evgeniy Polyakov
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=1112931238.28858.180.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=guillaume.thouvenin@bull.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@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