Heinz Mauelshagen wrote: > that's what the t_group type is for. I'm confused about what you meant by that--in the isw handler, the raid_devs created in _create_rd are suppsoed to have > Is there a reason, why you couldn't use that as already down > for Intel Software RAID (iswc.[ch]) and designed for other flavours > such as DDF ? Actually, I had no idea that isw was creating extra raid_devs in group_rd; from my perspective, I had simply thought that it made sense for read_raid_dev to create all the raid_devs that were required and to push all of those raid_devs through setup_rd, instead of creating one raid_dev per disk in read_raid_dev and adding the rest later. However, it seems a little weird to me that under that scheme one doesn't see all the raid_devs until after isw_group is called. But, I suppose it wouldn't be too difficult to reroll the patches to do it that way too. --D
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
