Thanks Ian for your helpful answer, you are right that is on Linux side but to clear my idea , the goal is to prioritize traffic that comes from different guest, for example if guest_1 is used for a voip server than it would be reasonable to schedule first the vif guest_1 before other guests. The diagram atached below explains better my idea. The goal is to improve the latency and jitter for real-time traffic which have critical requirements to QoS especially on heavy network i/o hosts, and if the vifs of different guest are scheduled on round robin manner in dom0 backend than we can improve this scheduling algorithm like using weighted round robin which can give more scheduling time to a vif that was used by a voip-server guest.
As a case considering an i/o heavy load network traffic host, i think it would be more efficient using a simple scheduler like weighted round robin or maybe others rather than using tools that may increase overhead . What do you think Ian ? Thanks Ronald On Tue, Feb 3, 2015 at 12:12 PM, Ian Campbell <ian.campb...@citrix.com> wrote: > On Tue, 2015-02-03 at 11:05 +0000, Wei Liu wrote: > > So if you want to change scheduler you're heading into instrumenting > > Linux's scheduler to meet your need. YMMW. > > Right, I'd expect this sort of network traffic scheduling/shaping to be > achievable with the normal Linux facilities for doing such things (i.e. > tc and friends) and if not then it is those which should be enhanced > rather than adding Xen specific stuff to netback (or else a convincing > reason for it being Xen specific should be given). > > The same goes for the other possible backend OSes, e.g. *BSDs > shaping/filtering facility, whatever it is called, should be used there. > > Ian. > > >
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
