I have a theoretical situation that I was hoping somebody would have an answer or two for. Here goes:
There are two servers, one aoe target (vblade) and an aoe initiator. The aoe target server shares disks to the aoe initiator. Situation: In the case that the aoe target backing storage has errors on a section of, for example, a raid5 array, the vblade hangs for a period of time and makes the aoe initiator wait or rexmit other concurrent IO requests until vblade gets past the slow/bad section of the raid5 array. Theoretical Fix: Could adding in a worker thread pool alleviate some of the "blocking" factor since vblade is single threaded and essentially runs sequentially? Where would locking have to be placed (if at all) and could this cause corruption? Thanks! -- Matth ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Aoetools-discuss mailing list Aoetools-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
