From: Neil Brown <neilb@suse.de>
To: Andre Noll <maan@systemlinux.org>
Cc: raziebe@gmail.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/6] md: Remove the hash tables from raid0 V2 -- Introduction.
Date: Sat, 16 May 2009 21:53:54 +1000 [thread overview]
Message-ID: <18958.43346.399343.631536@notabene.brown> (raw)
In-Reply-To: message from Andre Noll on Friday May 15
On Friday May 15, maan@systemlinux.org wrote:
> As mentioned by Neil, the raid0 hash table does probably not add
> any value and contains some rather strange code that manipulates the
> various sector counts needed to maintain this table.
>
> This patch series against Neil's for-next tree as of yesterday removes
> the hash table from the raid0 code.
Thanks.
All applied, and pushed out to
git://neil.brown.name/md for-next
I've added a couple more patches to remove a couple of fields from
struct strip_zone. I'll post them shortly for comment.
And thanks for finding the memory leak!
NeilBrown
prev parent reply other threads:[~2009-05-16 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 13:18 [PATCH 0/6] md: Remove the hash tables from raid0 V2 -- Introduction Andre Noll
2009-05-15 13:18 ` [PATCH 1/6] md: raid0: Replace hash table lookup by looping over all strip_zones Andre Noll
2009-05-15 13:18 ` [PATCH 2/6] md: raid0: Remove hash table Andre Noll
2009-05-15 13:18 ` [PATCH 3/6] md: raid0: Remove hash spacing and sector shift Andre Noll
2009-05-15 13:18 ` [PATCH 4/6] md: raid0: Make raid0_run() return a proper error code Andre Noll
2009-05-15 13:18 ` [PATCH 5/6] md: raid0: Allocate all buffers for the raid0 configuration in one function Andre Noll
2009-05-15 13:18 ` [PATCH 6/6] md: raid0: Fix a memory leak when stopping a raid0 array Andre Noll
2009-05-16 11:53 ` Neil Brown [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=18958.43346.399343.631536@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=maan@systemlinux.org \
--cc=raziebe@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 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).