From: Neil Brown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PULL REQUEST] md update for current merge window
Date: Fri, 29 Oct 2010 19:37:06 +1100 [thread overview]
Message-ID: <19658.34738.159280.954794@notabene.brown> (raw)
Hi Linus,
as detailed below, a few updates for md for 2.6.37.
Nothing really major. The most significant is a few improvements to
allocation of bios so we don't exhaust a global pool and so run the
risk of dead-lock when multiple md devices are stacked, or used with
something else (like swap) that allocates bios from the global pool.
Apart from that, minor bug fixes and clean-up.
Thanks,
NeilBrown
The following changes since commit 12ba8d1e9262ce81a695795410bd9ee5c9407ba1:
fix braino in fs: do not assign default i_ino in new_inode (2010-10-26 20:25:45 -0700)
are available in the git repository at:
git://neil.brown.name/md for-linus
NeilBrown (12):
md: Fix regression with raid1 arrays without persistent metadata.
md: remove md_mutex locking.
md: use sector_t in bitmap_get_counter
md: Fix possible deadlock with multiple mempool allocations.
md: use bio_kmalloc rather than bio_alloc when failure is acceptable.
md/raid1: perform mem allocation before disabling writes during resync.
md: change type of first arg to sync_page_io.
md: use separate bio pool for each md device.
md: unplug writes to external bitmaps.
md/raid1: discard unused variable.
md/raid1: fix some typos in comments.
md: tidy up device searches in read_balance.
Tejun Heo (1):
md: fix and update workqueue usage
drivers/md/bitmap.c | 30 ++++----
drivers/md/bitmap.h | 4 +-
drivers/md/faulty.c | 2 +-
drivers/md/md.c | 159 ++++++++++++++++++++++++++++--------
drivers/md/md.h | 8 ++-
drivers/md/raid1.c | 224 ++++++++++++++++++++++----------------------------
drivers/md/raid1.h | 2 -
drivers/md/raid10.c | 42 +++++-----
drivers/md/raid5.c | 6 +-
9 files changed, 272 insertions(+), 205 deletions(-)
reply other threads:[~2010-10-29 8:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19658.34738.159280.954794@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=torvalds@linux-foundation.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