From: Andreas Dilger <adilger@sun.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, tytso@mit.edu, sandeen@redhat.com,
linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH] Convert ext4_lock_group to use sb_bgl_lock
Date: Mon, 27 Apr 2009 23:00:16 -0600 [thread overview]
Message-ID: <20090428050016.GL3209@webber.adilger.int> (raw)
In-Reply-To: <1240860896-2011-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Apr 28, 2009 01:04 +0530, Aneesh Kumar wrote:
> +static inline spinlock_t *ext4_group_lock(struct super_block *sb, ext4_group_t group)
> {
> + return bgl_lock_ptr(EXT4_SB(sb)->s_blockgroup_lock, group);
> +}
>
> +static inline void ext4_lock_group(struct super_block *sb,ext4_group_t group)
> +{
> + spin_lock(ext4_group_lock(sb, group));
> }
I find it a bit confusing to have both ext4_group_lock() and ext4_lock_group()
as it isn't obvious without looking at the functions which one is which.
I'd rather have a function name like "ext4_group_lock_ptr()" or similar,
which is pretty unambiguous.
> -static void mb_set_bits(spinlock_t *lock, void *bm, int cur, int len)
> +static void mb_set_bits(void *bm, int cur, int len)
It also wouldn't be a terrible idea to make the mb_set_bits() function
arguments match the name/order of mb_set_bit():
static inline void mb_set_bit(int bit, void *addr)
static void mb_set_bits(void *bm, int cur, int len)
They should be "bit, addr" and "bit, addr, len", to be more consistent
with ext4_set_bit(). Stuff for a separate patch, however.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-04-28 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 19:34 [RFC PATCH] Convert ext4_lock_group to use sb_bgl_lock Aneesh Kumar K.V
2009-04-28 5:00 ` Andreas Dilger [this message]
2009-05-03 0:53 ` [PATCH] ext4: " Theodore Ts'o
2009-05-04 9:11 ` [PATCH -V2] " Aneesh Kumar K.V
2009-05-04 11:39 ` Theodore Tso
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=20090428050016.GL3209@webber.adilger.int \
--to=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).