<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pm24.git/drivers/md, branch v2.6.15</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.kobert.dev/pm24.git/atom?h=v2.6.15</id>
<link rel='self' href='https://git.kobert.dev/pm24.git/atom?h=v2.6.15'/>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/'/>
<updated>2005-12-20T00:47:50Z</updated>
<entry>
<title>[PATCH] md: Change case of raid level reported in sys/mdX/md/level</title>
<updated>2005-12-20T00:47:50Z</updated>
<author>
<name>Neil Brown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-12-20T00:07:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=bcb97940f31ded5ac551da8bfc849583203fc6f2'/>
<id>urn:sha1:bcb97940f31ded5ac551da8bfc849583203fc6f2</id>
<content type='text'>
I had thought that keeping the reported tail level clearly different
from the module name was a good idea, but I've changed my mind.

'raid5' is better and probably less confusing than 'RAID-5'.

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: use correct size of raid5 stripe cache when measuring how full it is</title>
<updated>2005-12-12T17:06:04Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-12-12T10:39:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=5036805be7b815eb18dcce489d974f3aee4f3841'/>
<id>urn:sha1:5036805be7b815eb18dcce489d974f3aee4f3841</id>
<content type='text'>
The raid5 stripe cache was recently changed from fixed size (NR_STRIPES) to
variable size (conf-&gt;max_nr_stripes).  However there are two places that still
use the constant and as a result, reducing the size of the stripe cache can
result in a deadlock.

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: fix a use-after-free bug in raid1</title>
<updated>2005-12-12T17:06:04Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-12-12T10:39:16Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=3795bb0fc52fe2af2749f3ad2185cb9c90871ef8'/>
<id>urn:sha1:3795bb0fc52fe2af2749f3ad2185cb9c90871ef8</id>
<content type='text'>
Who would submit code with a FIXME like that in it !!!!

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: fix --re-add for raid1 and raid6</title>
<updated>2005-11-28T22:42:26Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-11-28T21:44:13Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=6aea114a728db9296f42102d4885e7fb035de0a9'/>
<id>urn:sha1:6aea114a728db9296f42102d4885e7fb035de0a9</id>
<content type='text'>
If you have an array with a write-intent-bitmap, and you remove a device, then
re-add it, a full recovery isn't needed.  We detect a re-add by looking at
saved_raid_disk.  For raid1, it doesn't matter which disk it was, only whether
or not it was an active device.  The old code being removed set a value of
'mirror' which was then ignored, so it can go.  The changed code performs the
correct check.

For raid6, if there are two missing devices, make sure we chose the right slot
on --re-add rather than always the first slot.

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: set default_bitmap_offset properly in set_array_info</title>
<updated>2005-11-28T22:42:25Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-11-28T21:44:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=b2a2703c282ce77d189a250f58039daac1da3314'/>
<id>urn:sha1:b2a2703c282ce77d189a250f58039daac1da3314</id>
<content type='text'>
If an array is created using set_array_info, default_bitmap_offset isn't set
properly meaning that an internal bitmap cannot be hot-added until the array
is stopped and re-assembled.

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: fix problem with raid6 intent bitmap</title>
<updated>2005-11-28T22:42:25Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-11-28T21:44:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=b5ab28a3b81381103b686ff6b9d2f5fbb944bc8c'/>
<id>urn:sha1:b5ab28a3b81381103b686ff6b9d2f5fbb944bc8c</id>
<content type='text'>
When doing a recovery, we need to know whether the array will still be
degraded after the recovery has finished, so we can know whether bits can be
clearred yet or not.  This patch performs the required check.

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: fix locking problem in r5/r6</title>
<updated>2005-11-28T22:42:25Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-11-28T21:44:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=700e432d8364ce59c521abbe03a522051610ebc2'/>
<id>urn:sha1:700e432d8364ce59c521abbe03a522051610ebc2</id>
<content type='text'>
bitmap_unplug actually writes data (bits) to storage, so we shouldn't be
holding a spinlock...

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] md: improve read speed to raid10 arrays using 'far copies'</title>
<updated>2005-11-28T22:42:25Z</updated>
<author>
<name>NeilBrown</name>
<email>neilb@suse.de</email>
</author>
<published>2005-11-28T21:44:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=22dfdf5212e5864b844f629736fb993d4611f190'/>
<id>urn:sha1:22dfdf5212e5864b844f629736fb993d4611f190</id>
<content type='text'>
raid10 has two different layouts.  One uses near-copies (so multiple
copies of a block are at the same or similar offsets of different
devices) and the other uses far-copies (so multiple copies of a block
are stored a greatly different offsets on different devices).  The point
of far-copies is that it allows the first section (normally first half)
to be layed out in normal raid0 style, and thus provide raid0 sequential
read performance.

Unfortunately, the read balancing in raid10 makes some poor decisions
for far-copies arrays and you don't get the desired performance.  So
turn off that bad bit of read_balance for far-copies arrays.

With this patch, read speed of an 'f2' array is comparable with a raid0
with the same number of devices, though write speed is ofcourse still
very slow.

Signed-off-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] device-mapper raid1: drop mark_region spinlock fix</title>
<updated>2005-11-22T17:14:31Z</updated>
<author>
<name>Jonathan E Brassow</name>
<email>jbrassow@redhat.com</email>
</author>
<published>2005-11-22T05:32:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=7692c5dd48026d952199c2b97c3418f927cc0407'/>
<id>urn:sha1:7692c5dd48026d952199c2b97c3418f927cc0407</id>
<content type='text'>
The spinlock region_lock is held while calling mark_region which can sleep.
Drop the spinlock before calling that function.

A region's state and inclusion in the clean list are altered by rh_inc and
rh_dec.  The state variable is set to RH_CLEAN in rh_dec, but only if
'pending' is zero.  It is set to RH_DIRTY in rh_inc, but not if it is already
so.  The changes to 'pending', the state, and the region's inclusion in the
clean list need to be atomicly.

Signed-off-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] device-mapper snapshot: bio_list fix</title>
<updated>2005-11-22T17:14:31Z</updated>
<author>
<name>jblunck@suse.de</name>
<email>jblunck@suse.de</email>
</author>
<published>2005-11-22T05:32:36Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pm24.git/commit/?id=233886dd32ad71daf9c21bf3728c0933a94870f0'/>
<id>urn:sha1:233886dd32ad71daf9c21bf3728c0933a94870f0</id>
<content type='text'>
bio_list_merge() should do nothing if the second list is empty - not oops.

Signed-off-by: Alasdair G Kergon &lt;agk@redhat.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
</content>
</entry>
</feed>
