On Mon, Sep 13, 2010 at 07:00:51PM +0200, Avi Kivity wrote: > On 09/13/2010 06:30 PM, Michael S. Tsirkin wrote: > >Trouble is, each vhost-net device is associated with 1 tun/tap > >device which means that each vhost-net device is associated with a > >transmit and receive queue. > > > >I don't know if you'll always have an equal number of transmit and > >receive queues but there's certainly challenge in terms of > >flexibility with this model. > > > >Regards, > > > >Anthony Liguori > >Not really, TX and RX can be mapped to different devices, > >or you can only map one of these. What is the trouble? > > Suppose you have one multiqueue-capable ethernet card. How can you > connect it to multiple rx/tx queues? > tx is in principle doable, but what about rx? > > What does "only map one of these" mean? Connect the device with one > queue (presumably rx), and terminate the others? > > > Will packet classification work (does the current multiqueue > proposal support it)? > This is a non trivial problem, but this needs to be handled in tap, not in vhost net. If tap gives you multiple queues, vhost-net will happily let you connect vqs to these. > > -- > error compiling committee.c: too many arguments to function > > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
