On Tue, 2011-11-29 at 22:28 +0800, Asias He wrote: > Currently, all blk requests are processed in notify_vq() which is in > the context of ioeventfd thread: ioeventfd__thread(). The processing > in notify_vq() may take a long time to complete. > > We should make notify_vq() return as soon as possible, since all devices > are sharing the single ioeventfd thread. Otherwise, it will block other > device's notify_vq() being called and starve other devices. > > In virtio net's notify_vq(), we simply signal the tx/rx handle thread > and return. Why not use the threadpool? > > This patch makes virtio blk's notify_vq() just notify the blk thread > instead of doing the real hard read/write work. Tests show that the > overhead of the notification operations introduced by this patch is > small. > > Signed-off-by: Asias He <asias.hejun@xxxxxxxxx> > --- -- Sasha. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
