From: Anand Jain <Anand.Jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: looping across fs_devices isn't necessary
Date: Wed, 05 Feb 2014 21:02:21 +0800 [thread overview]
Message-ID: <52F2365D.7090609@oracle.com> (raw)
In-Reply-To: <1391605052-15198-1-git-send-email-anand.jain@oracle.com>
This patch was incomplete. Kindly ignore.
Thanks, Anand
On 02/05/14 08:57 PM, Anand Jain wrote:
> btrfs_show_devname() is trying to know dev name with
> lowest devid for a given FSID, so looping across the
> FSID isn't necessary
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> fs/btrfs/super.c | 18 +++++++-----------
> 1 files changed, 7 insertions(+), 11 deletions(-)
>
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 378157c..6ed76d8 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -1885,22 +1885,18 @@ static int btrfs_unfreeze(struct super_block *sb)
> static int btrfs_show_devname(struct seq_file *m, struct dentry *root)
> {
> struct btrfs_fs_info *fs_info = btrfs_sb(root->d_sb);
> - struct btrfs_fs_devices *cur_devices;
> struct btrfs_device *dev, *first_dev = NULL;
> struct list_head *head;
> struct rcu_string *name;
>
> mutex_lock(&fs_info->fs_devices->device_list_mutex);
> - cur_devices = fs_info->fs_devices;
> - while (cur_devices) {
> - head = &cur_devices->devices;
> - list_for_each_entry(dev, head, dev_list) {
> - if (dev->missing)
> - continue;
> - if (!first_dev || dev->devid < first_dev->devid)
> - first_dev = dev;
> - }
> - cur_devices = cur_devices->seed;
> +
> + head = &fs_info->fs_devices->devices;
> + list_for_each_entry(dev, head, dev_list) {
> + if (dev->missing)
> + continue;
> + if (!first_dev || dev->devid < first_dev->devid)
> + first_dev = dev;
> }
>
> if (first_dev) {
>
prev parent reply other threads:[~2014-02-05 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 12:57 [PATCH] btrfs: looping across fs_devices isn't necessary Anand Jain
2014-02-05 13:02 ` Anand Jain [this message]
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=52F2365D.7090609@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).