From: Ted Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: Amir Goldstein <amir73il@gmail.com>,
"Darrick J. Wong" <djwong@us.ibm.com>,
Sunil Mushran <sunil.mushran@oracle.com>,
Andi Kleen <andi@firstfloor.org>, Mingming Cao <cmm@us.ibm.com>,
Joel Becker <jlbec@evilplan.org>,
linux-ext4@vger.kernel.org, Coly Li <colyli@gmail.com>,
Yongqiang Yang <xiaoqiangnk@gmail.com>
Subject: Re: [PATCH] libext2fs: reserve exclude bitmap fields in group descriptor
Date: Thu, 15 Sep 2011 17:57:59 -0400 [thread overview]
Message-ID: <20110915215759.GG28181@thunk.org> (raw)
In-Reply-To: <F609F599-7286-4E6C-93B2-FEB9F9F5C077@dilger.ca>
On Thu, Sep 15, 2011 at 01:08:34PM -0600, Andreas Dilger wrote:
> In that light, why not continue to use an inode to map the exclude bitmap
> blocks, where the bitmap offset is (group * blocksize), instead of
> explicitly listing all of the blocks in the group descriptor? This is
> how the buddy bitmap works in memory only, but it could be done for the
> exclude bitmap on disk.
I seem to recall the use of an inode to map the exclude bitmap added a
huge amount of complexity to the snapshot patches. Amir, am I
remembering this correctly?
- Ted
next prev parent reply other threads:[~2011-09-15 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 6:50 [PATCH] libext2fs: reserve exclude bitmap fields in group descriptor Amir Goldstein
2011-09-15 10:06 ` Andreas Dilger
2011-09-15 14:03 ` Amir Goldstein
2011-09-15 14:21 ` Ted Ts'o
2011-09-15 13:16 ` Ted Ts'o
2011-09-15 13:47 ` Amir Goldstein
2011-09-15 19:08 ` Andreas Dilger
2011-09-15 21:57 ` Ted Ts'o [this message]
2011-09-16 6:45 ` Amir Goldstein
2011-09-16 11:43 ` Yongqiang Yang
2011-09-16 20:22 ` Andreas Dilger
2011-09-16 6:55 ` Amir Goldstein
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=20110915215759.GG28181@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=amir73il@gmail.com \
--cc=andi@firstfloor.org \
--cc=cmm@us.ibm.com \
--cc=colyli@gmail.com \
--cc=djwong@us.ibm.com \
--cc=jlbec@evilplan.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sunil.mushran@oracle.com \
--cc=xiaoqiangnk@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.