Skip to contentSkip to conversation

raid5: Offload RAID operations to a workqueue

PATCH In review Dan Williams 2 participants 2 messages Jun 28, 2006 – Jun 29, 2006 MD RAID

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 raid5: Offload RAID operations to a workqueue

This patch set is a step towards enabling hardware offload in the md-raid5 driver. These patches are considered experimental and are not yet suitable for production environments.

As mentioned, this patch set is the first step in that it moves work from handle_stripe5 to a work queue. The next step is to enable the work queue to offload the operations to hardware copy/xor engines using the dmaengine API (include/linux/dmaengine.h). Initial testing shows that about 60% of the array maintenance work previously performed by raid5d has moved to the work queue.

These patches apply to the version of md as of commit 266bee88699ddbde42ab303bbc426a105cc49809 in Linus' tree.

Regards,

Dan Williams

[PATCH 001 of 006] raid5: Move write operations to a work queue [PATCH 002 of 006] raid5: Move check parity operations to a work queue [PATCH 003 of 006] raid5: Move compute block operations to a work queue [PATCH 004 of 006] raid5: Move read completion copies to a work queue [PATCH 005 of 006] raid5: Move expansion operations to a work queue [PATCH 006 of 006] raid5: Remove compute_block and compute_parity

#1 lore raw
Quoted 6 lines · Dan Williams

This patch set is a step towards enabling hardware offload in the md-raid5 driver. These patches are considered experimental and are not yet suitable for production environments.

As mentioned, this patch set is the first step in that it moves work from handle_stripe5 to a work queue.

Hi,

since using work queues involve more context switches than doing things inline... have you measured the performance impact of your changes? If so... was there any impact that you could measure, and how big was that?

Greetings,
Arjan van de Ven