From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Clements <paul.clements@steeleye.com>
Subject: [PATCH 000 of 8] md/bitmap: Introduction - rework management of bitmap files.
Date: Fri, 12 May 2006 16:07:25 +1000 [thread overview]
Message-ID: <20060512160121.7872.patches@notabene> (raw)
I thought it was time to review the md/bitmap code - partly because I
wasn't comfortable with how it was handling writing to files. The more
I learnt about the VM/VFS, the more I realised it was wrong....
I found plenty to do...
The last patch in this series of 8 is the big one. It substantially
changes the way bitmap files are handled. The key change is that it
now works more like swapfile: bmap() is used to find where the blocks
are and write goes direct to storage bypassing the filesystem.
These are *not* for 2.6.17, but should be ok for when 2.6.18 opens.
I've done some testing and it seems to work OK, but it is a big change
and more testing wouldn't be a bad thing :-)
[PATCH 001 of 8] md/bitmap: Fix online removal of file-backed bitmaps
[PATCH 002 of 8] md/bitmap: Remove bitmap writeback daemon.
[PATCH 003 of 8] md/bitmap: Cleaner separation of page attribute handlers in md/bitmap.
[PATCH 004 of 8] md/bitmap: Use set_bit etc for bitmap page attributes.
[PATCH 005 of 8] md/bitmap: Remove unnecessary page reference manipulations from md/bitmap code.
[PATCH 006 of 8] md/bitmap: Remove dead code from md/bitmap.
[PATCH 007 of 8] md/bitmap: Tidy up i_writecount handling in md/bitmap
[PATCH 008 of 8] md/bitmap: Change md/bitmap file handling to use bmap to file blocks.
next reply other threads:[~2006-05-12 6:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 6:07 NeilBrown [this message]
2006-05-12 6:07 ` [PATCH 001 of 8] md/bitmap: Fix online removal of file-backed bitmaps NeilBrown
2006-05-12 6:07 ` [PATCH 002 of 8] md/bitmap: Remove bitmap writeback daemon NeilBrown
2006-05-12 17:40 ` Andrew Morton
2006-05-13 3:14 ` Neil Brown
2006-05-13 6:59 ` Andrew Morton
2006-05-12 6:07 ` [PATCH 003 of 8] md/bitmap: Cleaner separation of page attribute handlers in md/bitmap NeilBrown
2006-05-12 6:07 ` [PATCH 004 of 8] md/bitmap: Use set_bit etc for bitmap page attributes NeilBrown
2006-05-12 6:07 ` [PATCH 005 of 8] md/bitmap: Remove unnecessary page reference manipulations from md/bitmap code NeilBrown
2006-05-12 6:07 ` [PATCH 006 of 8] md/bitmap: Remove dead code from md/bitmap NeilBrown
2006-05-12 6:08 ` [PATCH 007 of 8] md/bitmap: Tidy up i_writecount handling in md/bitmap NeilBrown
2006-05-12 6:08 ` [PATCH 008 of 8] md/bitmap: Change md/bitmap file handling to use bmap to file blocks NeilBrown
2006-05-12 17:47 ` Andrew Morton
2006-05-13 3:46 ` Neil Brown
2006-05-13 6:59 ` Andrew Morton
2006-05-13 15:29 ` Paul Clements
2006-05-13 15:42 ` Andrew Morton
2006-05-14 11:15 ` Neil Brown
2006-05-14 11:22 ` Andrew Morton
2006-05-15 0:26 ` Neil Brown
2006-05-15 21:04 ` Andrew Morton
2006-05-15 23:03 ` Neil Brown
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=20060512160121.7872.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=paul.clements@steeleye.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 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).