On Sul, 2004-07-11 at 21:17, Jeff Garzik wrote:
> 1) Transaction sequencing. Consider that N disk transactions comprise a
> single RAID1 write. The hardware can be set up to wait until all N
> transactions are complete, before sending an interrupt. This is
> applicable to Marvell and Promise SATA, among others.
So this is basically IRQ mitigation. Can you flip the "cause an IRQ"
status on the fly ?
> 2) Copy elimination. All disk transactions on the Promise SX4 go
> through an on-board DIMM (128M - 2G), before being sent to the attached
> controllers. I would love to use this to eliminate data duplication on
> RAID1 and RAID5 writes.
Big win for PCI cards because it cuts PCI bandwidth way down. It
doesn't seem like it should be that hard to add to the drivers either
depending upon how the RAM is presented. Is it mapped into PCI space ?
> Or maybe, allow the user to set a flag that tells md to pass a request
> directly through to the low-level driver, in certain situations ("pass
> through all RAID1 writes, but handle everything else in software"). /me
> thinks out loud...
As some kind of driver "md_ops" or as a separate raid1-promise plugin ?
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
