exofs changes for 2.6.34
in [Kernel]
|
Prev: [PATCH 2/2] DMAENGINE: COH 901 318 fix bytesleft
Next: [PATCH 12/14] perf, x86: Expose the full PEBS record using PERF_SAMPLE_RAW
From: Christoph Hellwig on 4 Mar 2010 09:10 On Thu, Mar 04, 2010 at 02:10:57PM +0200, Boaz Harrosh wrote: > Next changes will be support for raid5 and raid6 Err, you're not pushing another bloody copy of raid algorithms in, are you? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Boaz Harrosh on 7 Mar 2010 03:40
On 03/04/2010 04:00 PM, Christoph Hellwig wrote: > On Thu, Mar 04, 2010 at 02:10:57PM +0200, Boaz Harrosh wrote: >> Next changes will be support for raid5 and raid6 > > Err, you're not pushing another bloody copy of raid algorithms in, are > you? > No of course not. You should know me by now. I intend to fully reuse both linux/raid/pq.h and linux/async_tx.h. [What? lose all these CPU/HW optimizations people have done ?-)] I'm struggling with re-factoring some of drivers/md/raid* as I'm using bios just as they do, and bio_lists are fine, but currently the code is very md/dm structure specific, there is no abstract bio_list API but I hope I can extract one with minimum risk. I have not yet looked into btrfs, they do raid5 as well right? But all this is far down the road, off course I'll send RFCs first. The above push is just for that unique objects groups/striping/mirroring, which is very small code, a couple of functions actually, over the basic IO. Thanks for asking, though. Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |