From: Nick Piggin <npiggin@suse.de>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [RFC] non-refcounted pages, application to slab?
Date: Wed, 25 Jan 2006 12:18:29 +0100 [thread overview]
Message-ID: <20060125111829.GD30421@wotan.suse.de> (raw)
In-Reply-To: <43D75CB8.9090101@cosmosbay.com>
On Wed, Jan 25, 2006 at 12:10:48PM +0100, Eric Dumazet wrote:
>
> So we cannot change atomic_dec_and_test(atomic_t *v) but introduce a new
> function like :
>
> int atomic_dec_refcount(atomic_t *v)
> {
> #ifdef CONFIG_SMP
> /* avoid an atomic op if we are the last user of this refcount */
> if (atomic_read(v) == 1) {
> atomic_set(v, 0); /* not a real atomic op on most machines */
> return 1;
> }
> #endif
> return atomic_dec_and_test(v);
> }
>
> The cost of the extra conditional branch is worth, if it can avoid an
> atomic op.
>
If it can always avoid an atomic op then the conditional branch is
useless, and if it can avoid the atomic op in 20% of cases then it
might still be useless (especially considering the extra icache).
Actual measurements would be required I think.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-01-25 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 9:39 Nick Piggin
2006-01-25 9:54 ` Eric Dumazet
2006-01-25 9:56 ` Nick Piggin
2006-01-25 10:26 ` Eric Dumazet
2006-01-25 10:57 ` Nick Piggin
2006-01-25 11:10 ` Eric Dumazet
2006-01-25 11:18 ` Nick Piggin [this message]
2006-01-25 10:30 ` Pekka Enberg
2006-01-25 11:00 ` Nick Piggin
2006-01-25 11:19 ` Pekka Enberg
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=20060125111829.GD30421@wotan.suse.de \
--to=npiggin@suse.de \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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