Skip to contentSkip to conversation

Silly stripe cache values

PATCH In review Brad Campbell 2 participants 4 messages Mar 25, 2006 – Mar 30, 2006 MD RAID

lore
Share & tools
lore
#0 lore raw

G'day all,

I have a box here.. it has a 2Ghz processor and 1.5GB of ram. It runs the entire OS over NFS and it's sole purpose in life is to run 15 SATA drives in a Raid-6 with ext3 on it, and share that over NFS. Most of that ram is sitting completely idle and thus I thought a logical thing to do would be to stuff as much of it as possible into the MD subsystem to help it cache..

Are there any limits to the values living in /sys/block/md* and what might be the tradeoffs (if any) to using what would normally be thought stupid amounts of ram for these knobs ?

This box does not get written to often, it's just a media streamer mostly.. but if I am writing to it then it chokes just providing a 1Mb stream over the network currently. (It's on a 2.6.15-git11 kernel currently but I'm just upgrading to 2.6.16 now)

Regards,
Brad

Signature · 3 lines
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
#1 lore raw
Quoted 7 lines · Brad Campbell

G'day all,

I have a box here.. it has a 2Ghz processor and 1.5GB of ram. It runs the entire OS over NFS and it's sole purpose in life is to run 15 SATA drives in a Raid-6 with ext3 on it, and share that over NFS. Most of that ram is sitting completely idle and thus I thought a logical thing to do would be to stuff as much of it as possible into the MD subsystem to help it cache..

Are there any limits to the values living in /sys/block/md* and what might be the tradeoffs (if any) to using what would normally be thought stupid amounts of ram for these knobs ?

This box does not get written to often, it's just a media streamer mostly.. but if I am writing to it then it chokes just providing a 1Mb stream over the network currently. (It's on a 2.6.15-git11 kernel currently but I'm just upgrading to 2.6.16 now)

Scratch that.. the limit appears to be 32768 and that works fine..

Google search results increase in accuracy proportionally with the elapsed time of a list posting with the question.. :\

Brad

Signature · 3 lines
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
#2 lore raw

PATCH 1/1 Add stripe cache entries to raid6 sysfs

Raid-6 did not create sysfs entries for stripe cache

---

drivers/md/raid6main.c 2006-03-25 16:35:05.000000000 +0400 renamed from linux-2.6.16/drivers/md/raid6main.c 2006-03-20 09:53:29.000000000 +0400 +1 -0
diff -u vanilla/linux-2.6.16/drivers/md/raid6main.c linux-2.6.16/drivers/md/raid6main.c
@@ -2148,6 +2148,7 @@
        }
 
        /* Ok, everything is just fine now */
+        sysfs_create_group(&mddev->kobj, &raid6_attrs_group);
        mddev->array_size =  mddev->size * (mddev->raid_disks - 2);
 
        mddev->queue->unplug_fn = raid6_unplug_device;

---

Signature · 3 lines
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
#3 lore raw

Re: [PATCH] Add stripe cache entries to raid6 sysfs

Quoted 9 lines · On Saturday March 25, [email protected] wrote:

Raid-6 did not create sysfs entries for stripe cache

---
diff -u vanilla/linux-2.6.16/drivers/md/raid6main.c linux-2.6.16/drivers/md/raid6main.c

drivers/md/raid6main.c 2006-03-25 16:35:05.000000000 +0400 line 2154

Quoted 7 lines
drivers/md/raid6main.c 2006-03-25 16:35:05.000000000 +0400 renamed from linux-2.6.16/drivers/md/raid6main.c 2006-03-20 09:53:29.000000000 +0400 +1 -0
@@ -2148,6 +2148,7 @@
         }
 
         /* Ok, everything is just fine now */
+        sysfs_create_group(&mddev->kobj, &raid6_attrs_group);
         mddev->array_size =  mddev->size * (mddev->raid_disks - 2);
 
         mddev->queue->unplug_fn = raid6_unplug_device;

Gee, I wonder I missed that...
Thanks!

NeilBrown