From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <josef@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
viro@ZenIV.linux.org.uk, hch@infradead.org
Subject: Re: [RFE] Add a new super operation for finding block devices in a super
Date: Mon, 14 Mar 2011 12:31:26 -0400 [thread overview]
Message-ID: <20110314163126.GA13784@infradead.org> (raw)
In-Reply-To: <1300117060-13613-1-git-send-email-josef@redhat.com>
I think there's a better and more efficient way to archive this.
We already have a bd_super field in struct block_device. Just
generalize it, and use it from the freeze code instead of doing the
get_active_super loop.
next prev parent reply other threads:[~2011-03-14 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 15:37 [RFE] Add a new super operation for finding block devices in a super Josef Bacik
2011-03-14 15:37 ` [PATCH 1/2] fs: add super operation contains_bdev Josef Bacik
2011-03-14 15:37 ` [PATCH 2/2] btrfs: implement super op contains_bdev Josef Bacik
2011-03-14 16:31 ` Christoph Hellwig [this message]
2011-03-14 17:50 ` [RFE] Add a new super operation for finding block devices in a super Josef Bacik
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=20110314163126.GA13784@infradead.org \
--to=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).