[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] remus network buffering configuraion

  • To: xen-users@xxxxxxxxxxxxx
  • From: 张伟 <zhangwqh@xxxxxxx>
  • Date: Mon, 23 Dec 2013 05:32:55 +0800 (CST)
  • Delivery-date: Sun, 22 Dec 2013 21:34:04 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Hi all,

Does anybody know that the function of ifb in xen remus project? I can not understand why remus network buffering needs ifb device. In new xen and linux version, the kernel qdisc module sch_plug provides the network buffering. If a virtual machine - eg domain id is 1. In domain0, vif is vif1.0(tc qdisc add dev vif1.0 root plug). Why not directly use the plug qdisc on this vif1.0. Remus needs to  use ifb device. The packets of vif1.0 needs to redirect to ifb0. 

ip link set ifb0 up

tc qdisc add dev ifb0 root plug

tc qdisc add dev vif1.0 ingress

tc filter add dev  vif1.0  parent ffff: proto ip pref 10 u32 match u32 0 0 action mirred egress redirect dev ifb0

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.