From: Sven Eckelmann <sven@narfation.org>
To: linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sven Eckelmann <sven@narfation.org>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: [PATCHv4 07/11] ext4: Use *_dec_not_zero instead of *_add_unless
Date: Wed, 27 Jul 2011 11:47:46 +0200 [thread overview]
Message-ID: <1311760070-21532-7-git-send-email-sven@narfation.org> (raw)
In-Reply-To: <1311760070-21532-1-git-send-email-sven@narfation.org>
atomic_dec_not_zero is defined for each architecture through
<linux/atomic.h> to provide the functionality of
atomic_add_unless(x, -1, 0).
Signed-off-by: Sven Eckelmann <sven@narfation.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: linux-ext4@vger.kernel.org
---
fs/ext4/ext4.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index fa44df8..29996e8 100644
--- a/fs/ext4/ext4.h
+++ b/fs/ext4/ext4.h
@@ -2098,7 +2098,7 @@ static inline void ext4_lock_group(struct super_block *sb, ext4_group_t group)
* We're able to grab the lock right away, so drop the
* lock contention counter.
*/
- atomic_add_unless(&EXT4_SB(sb)->s_lock_busy, -1, 0);
+ atomic_dec_not_zero(&EXT4_SB(sb)->s_lock_busy);
else {
/*
* The lock is busy, so bump the contention counter,
--
1.7.5.4
next prev parent reply other threads:[~2011-07-27 9:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 9:47 [PATCHv4 01/11] atomic: add *_dec_not_zero Sven Eckelmann
[not found] ` <1311760070-21532-1-git-send-email-sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org>
2011-07-27 9:47 ` [PATCHv4 02/11] batman-adv: Remove private define of atomic_dec_not_zero Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-27 9:47 ` [PATCHv4 03/11] fault_inject: " Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-27 9:47 ` [PATCHv4 04/11] PM: Use *_dec_not_zero instead of *_add_unless Sven Eckelmann
2011-07-27 19:50 ` Rafael J. Wysocki
2011-07-27 20:36 ` Pavel Machek
2011-07-27 20:36 ` Pavel Machek
2011-07-28 21:43 ` Rafael J. Wysocki
2011-07-28 21:43 ` Rafael J. Wysocki
2011-07-27 9:47 ` [PATCHv4 05/11] omap3isp: " Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-31 15:00 ` Laurent Pinchart
2011-08-01 10:07 ` Sven Eckelmann
2011-08-01 11:10 ` Laurent Pinchart
2011-08-01 11:10 ` Laurent Pinchart
2011-07-27 9:47 ` [PATCHv4 06/11] qeth: " Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann [this message]
2011-07-27 9:47 ` [PATCHv4 07/11] ext4: " Sven Eckelmann
2011-07-27 9:47 ` [PATCHv4 08/11] xfs: " Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-27 9:47 ` [PATCHv4 09/11] memcg: " Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-27 11:58 ` Michal Hocko
2011-07-27 9:47 ` [PATCHv4 10/11] drop_monitor: " Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-27 10:59 ` Neil Horman
2011-07-27 10:59 ` Neil Horman
2011-07-27 11:52 ` Sven Eckelmann
2011-07-27 14:25 ` Neil Horman
2011-07-27 14:25 ` Neil Horman
2011-07-27 9:47 ` [PATCHv4 11/11] Phonet: " Sven Eckelmann
2011-07-27 9:47 ` Sven Eckelmann
2011-07-27 10:29 ` Rémi Denis-Courmont
2011-08-02 9:58 ` [PATCHv4 01/11] atomic: add *_dec_not_zero Ralf Baechle
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=1311760070-21532-7-git-send-email-sven@narfation.org \
--to=sven@narfation.org \
--cc=adilger.kernel@dilger.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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